yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] icu64:
What's emmc support? I thought that was the internal memory
[Nexus 4 Original Android Development] thomas.raines:
The term eMMC is short for "embedded Multi-Media Controller" and refers to a package consisting of both flash memory and a flash memory controller integrated on the same silicon die. The eMMC solution consists of at least three components - the MMC (multimedia card) interface, the flash memory, and the flash memory controller.

The commit I'm guessing that your are refering to is "add 5.0 emmc support", which was an upstream commit from google simply changes the version number to make it more in line with Android 5.0 (Lollipop).

The Nexus 4 has always had eMMC support, but it does have to periodically updated like everything else. So, the key note in that particular commit is that it is "5.0" compliant.
[Nexus 4 Original Android Development] Horizone:
1. Do you have any specific recommended kernel settings?

2. Which version of the kernel is compatible with android 4.4.2?
[Nexus 4 Original Android Development] thomas.raines:
I recommend:

Under clock to 1242

Under volt to 600

Lionheart governor

and leave everything else at the default setting

Nexus4-LightningZap_p4.4.-3.3 was the last version for kitkat roms...
[Nexus 4 Original Android Development] Horizone:
Thank you :) But what about a balanced profile and a performance profile settings? Should we leave them on default?
[Nexus 4 Original Android Development] gorilla p:
You can't undervolt to 600mv on this device. Going below 700 on fast-binned gets unstable.
[Nexus 4 Original Android Development] thomas.raines:
I leave them as default... but it's a matter of preference...

I have kept my phone undervolted to 600mV since June now with NO issues. Granted no 2 CPU's are identical, but "fast binned" as you put it (usually it's referred to as normal, medium, and high binning) doesn't make it impossible to undervolt to -200mV from stock. What does matter is that the kernel code is clean, the kernel itself is stable, and how you use your device. If you are overclocking, I would not recommend undervolting below 700mV. But, following my recommendations listed a few post earlier, then most users won't have an issue, and more importantly won't see a huge drop in performance.

Since I got the clocking speeds and voltages straightened out MONTHS ago, I (and I'm sure several others) have had quite success with undervolting to 600mV.
[Nexus 4 Original Android Development] Flak:
He puts it as that cause that is what it is. Mako is binned at 4 levels, Slow/Normal/Fast/Fastest.
[Nexus 4 Original Android Development] elliot2112:
I don't know if this is a dumb question so bare with me. Is 5.0.1 version compatible if the ROM I'm running is 5.0.2?
[Nexus 4 Original Android Development] gorilla p:
Yeah and hearing 600mv is strange. I've never seen any N4 kernel with stock settings below 81mhz@750mv and even that caused some problems for people.

If I set me phone (fast binned) [MENTION=1601421]600[/MENTION] it will go full-retard.

Mine starts getting a little sketchy below 700mv.

I suspect most others will as well.

Can anyone confirm that they have UVd their mako to 600 without their device crashing and rebooting?

Also, I believe all Qualcomm CPUs come binned 1-4

slow, nominal, fast, faster.

http://www.oppoforums.com/threads/q...yours-slow-nominal-fast-or-faster.2842/page-2
[Nexus 4 Original Android Development] thomas.raines:
This may be, but I have had great success with undervolting to 600mV. I don't personally over clock, but I adjusted the voltages to compensate when oc'd and still allowing the end user to be underclocked as low as 600mV. I'm not here to argue with you as to what does and what doesn't work. If you don't like my work, move the hell on and leave me alone! If you do, hit the thanks button and move the hell on...
[Nexus 4 Original Android Development] elliot2112:
Will this work on 5.0.2?
[Nexus 4 Original Android Development] roguesyko:
Yes it will
[Nexus 4 Original Android Development] thomas.raines:
Want to try the best 5.X ROM out there? BrokenOs

If things keep going the way they are with XDA, I will be shutting this thread down. The Dysfunctional Family (my BroeknOs family and I), have created our own forum.
[Nexus 4 Original Android Development] BxingFetus:
Hey Thomas could I pm you about an issue I think I've found with brokenOs?
[Nexus 4 Original Android Development] thomas.raines:
Yes... or you could go to the broken os forums and post in the mako thread there...
[Nexus 4 Original Android Development] BxingFetus:
Actually there's no issue. My misunderstanding.
[Nexus 4 Original Android Development] thomas.raines:
Update to 5.0.2

Download now available...

Enjoy folks!!!!!!!!!!!!!!
[Nexus 4 Original Android Development] Gemichi:
Is it normal that it stuck at the Google logo after flashing and reboot?
[Nexus 4 Original Android Development] thomas.raines:
Sometimes it will seem to be stuck at the Google logo, but not for more than a few minutes (less than 5)...

What ROM?

Get a dmesg?

Did you flash in multirom?

Did you change any of the pre-set parameters in the installer, and if so, which ones?
[Nexus 4 Original Android Development] Gemichi:
Using barebone rom whick is simpleaosp. Only checked the dimmer screen brightness. No multirom. Dmesg?
[Nexus 4 Original Android Development] thomas.raines:
dmesg is a kernel log. Kind of like logcat, but if you don't pull it at the right time, you may never get it. Odd that it didn't boot on barebone. I'm downloading it now to see if I have any issues with it...

**EDIT**

I flashed the current version of barebones (simplae aosp) rom, broken gapps minimal, and Lightning Zap! 5.0.2 (curretn version) and had NO boot issues or any other issues. With that said, I don't have supersu handy to flash. Since my ROM BorkenOs has it built in natively, I didn't think I would need it...

But none-the-less, I'm not sure why you had issues.

Try flashing ROM, gapps, Lightning Zp!

reboot and setup rom

reboot to recovery

flash supersu (might try an older version

reboot

and let me know how it turns out...
[Nexus 4 Original Android Development] CrazyGamerGR:
awesome
[Nexus 4 Original Android Development] Medel-Silver:
Same problem here :(
[Nexus 4 Original Android Development] thomas.raines:
What rom?

Are you using multiboot?

Can you grab a dmesg log?

Did you change any of the default settings in the installer (which is ok if you did), and if you did, which ones?
[Nexus 4 Original Android Development] thomas.raines:
Update 5.1.0 available. Check changelog for links and details.

For you guys and gals that are getting stuck on the Google screen or having reboots, run the installer again, but change the minimum voltage to 700MHz. That seems to have fixed it for some people who have a slower binned cpu...
[Nexus 4 Original Android Development] Medel-Silver:
Your rom, brokenOS.

No multiboot.

I tried default settings, and tried with more voltage, same problem, only boot if I install other kernel, when I have time I will try again, thanks

P.D. Nominal binned CPU
[Nexus 4 Original Android Development] thomas.raines:
You're not still trying to flash supersu are you? Is it a fresh install? Try installing BrokenOs with only Gapps on a fresh install. Lightning Zap! kernel is native for the ROM (just won't have the setup options as you do with the standalone)
[Nexus 4 Original Android Development] Medel-Silver:
This is how I do, only flash rom and gapps, clean install, and don't boot
[Nexus 4 Original Android Development] thomas.raines:
Did you update your bootloader?

When it gets stuck at the Google screen, hold the power button and volume down button until it boot into bootloader, then select recovery, connect it to your computer and pull a dmesg for me please?

And when you do a clean install, you are wiping data, system, dalvik (art), and cache right?
[Nexus 4 Original Android Development] Medel-Silver:
Bootloader is updated.

When I have time I try it and send you dmesg.

I wipe everything.
[Nexus 4 Original Android Development] thomas.raines:
In an adb shell, type

dmesg|grep acpu

and give me the output
[Nexus 4 Original Android Development] thomas.raines:
Update 5.1.1 now available.

Check OP for link

A little explination:

My hdd that I use for development is formatted to btrfs. What I didn't know is btrfs uses checksums on EVERY file. I got a corrupted file which in turn corrupted the entire drive, and I had to wipe it. I didn't have a backup of it at all and kinda had to start over from scratch. Which means I screw something up between the installer scripts and my build scripts. It's all fixed up now though. I do apologize for my derp, and hope it don't happen again.

On a side note. I would strongly suggest wiping dalvik (art) and cache before flashing. If not, your device may shutdown immediately after it is done booting. Nothing to really worry about, just simply hold the power button for a few seconds till the google screen appears, and you should be good.

Guys and gals with slow binned cpus, MAKE SURE YOU SET THE MIN VOLTAGE TO 700. Or you will get random reboots like crazy.

if you want to know what your cpu is binned at, plug your phone into your computer, start and adb shell and type

dmesg|grep PVS

You will get an output of PVS 0-6

0 being slowest and 6 being fastest

Anyone with a 3, I would like to have you do some testing for me.
[Nexus 4 Original Android Development] thomas.raines:
Update available.

I'm calling EOL on this one guys and gals. I recently got a new Nexus 6 and am moving on. I will continue to maintain the BrokenOs builds for a little longer.

I would like to thank everyone for their support along the way. This has been one of the better devices and forums I have belonged to here on XDA. Again, thanks ya'll and enjoy!
[Nexus 5 Q&A, Help & Troubleshooting] thegod2012:
How's the battery life on this nexus is it anything close to the motox
[Nexus 5 Q&A, Help & Troubleshooting] GUGUITOMTG4:
Hi, here you can read many users impressions about nexus 5 battery life. http://xdaforums.com/google-nexus-5/general/nexus-5-battery-life-charge-t2511016
[Nexus 5 Q&A, Help & Troubleshooting] thegod2012:
Thank u
[Nexus 5 Q&A, Help & Troubleshooting] :
Try looking through some if this...

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

For me personally, both are excellent. I've taken much care getting the most from my batteries tho. I don't run a lot of services, greenify, screen as dim as I can comfortably use and I don't game.

I'd say the Moto x is a bit better, but not by much. I can get over 24 hours total and 6+ screen hours on both. Again....running very lean and mean tho. Don't expect these times with all the bells and whistles running. ;)

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Galaxy S 4 Q&A, Help & Troubleshooting] misterican:
SPH-L720

MF9

Ok, you must be wondering why the heck anyone would want to downgrade from 4.4.2. Well I had one noob moment and a couple of unfortunate coincidences. I haphazardly flashed a rom for an I9505g onto my phone. Luckly I can still boot up and connect to my wifi. If I turn the airplane mode off then the phone goes haywire. Im sure that isnt fixable.

My difficulty is finding a stock 4.2.2 ROM to flash.

I would just flash the recovery i have, but, it somehow is corrupt and sends my phone into a bootloop so i have to reflash the 4.4.2 again to get anything to work. Really, i think all i need is a link to get me going in the right direction for the files i need. If anyone could hook me up i'd really appreciate it.
[Galaxy S 4 Q&A, Help & Troubleshooting] s4lte100:
You are looking for 4.2.2?

When I was looking I found in

androidhilfe de

4pda

and Filecrop search

but my phone is I9505 I'm not sure whether your model but try
[Galaxy S 4 Q&A, Help & Troubleshooting] misterican:
Unfortunately, my phone is an sph-l720. It being a german site they dont even mention my model anywhere on that site.
[Galaxy S 4 Q&A, Help & Troubleshooting] s4lte100:
here in xda will not?

Google it has everything - you just have to browse
[Galaxy S 4 Q&A, Help & Troubleshooting] radkor:
You can't downgrade from 4.4 to any lower versions. Read forums...

TapTap@SGS4
[Galaxy S 4 Q&A, Help & Troubleshooting] Joku1981:
Wipe all and flash again android 4.4.2 for ur phone -> HERE. Dont play with fire.... :P
[Galaxy S 4 Q&A, Help & Troubleshooting] m_beek:
But I've Downgraded Many time from kitkat to JB4.3 without any problem
[Galaxy S 4 Q&A, Help & Troubleshooting] radkor:
Aaah, I see. You're on stock 4.2.2 and you've flashed 4.4.2 without flashing bootloader?

I thought you were on full stoc 4.4.2 with Knoxed BL. ;)

TapTap@SGS4
[8125, K-JAM, P4300, MDA Vario General] bubism:
Hi,

yesterday I field-tested HitchHiker (latest available version) on my Wiz, and it worked quite well. The only problem - one I had already experienced with the earlier ROM version - is that after using it once the Wizard begins behaving strange. Namely:

- Slower menu response

- Softkeys sometimes not working

- The power button takes several tries to actually get the device off

Is this just me, or is somebody else experiencing the same problems?

I'm beginning to think the problems come from some inter-app incompatibility (who knows... maybe HitchHiker doesn't like the G-protocol enabler, or something like that)... any suggestion/solution?

Also, I'm welcoming suggestions for other wardriving apps WITH a sensible option to connect to found APs (WiFiFoFum, in example, is very stylish but won't allow you to select a specific AP to connect to when you want to)...

Thank you in advance for your help!
[8125, K-JAM, P4300, MDA Vario General] pat12:
Well, I don' know about hitchhiker but like you, I came to be very dissapointed with wififofum so I switched to Wifi companion and I'm very happy with it, no glitches whatsoever
[8125, K-JAM, P4300, MDA Vario General] DynaMight:
Wifi companion was pretty good but my trail ran out :( but after I sorted out the Hitchhiker crashing problem (make sure you register your MSN details, although you dont actually have to connect) I havent had any issues at all, seems quite stable.
[8125, K-JAM, P4300, MDA Vario General] bubism:
Huh?

Are you saying that adding a profile in Msn Messenger makes Hitchhiker stable?

It makes no sense at all... but since even HH's installation is crazy, I'm trying it anyway...
[8125, K-JAM, P4300, MDA Vario General] MPIIIMan:
I can vouch for that post about Pocket MSN registering.

I don't know what it is.

When hitchhikers goes to connect to a wifi point, it tries to connect to google to verify connectivity on the wifi, and then it sends up a notification saying connected.

Just before that notification pops up, my hitchhiker would always crash. That is until I filled out Pocket MSN info (After seeing to do that in another thread)

I know it's crazy. Doesn't make any sense what so ever.
[8125, K-JAM, P4300, MDA Vario General] n7wtf:
Worked for me

Just tried it and it works fine. Just another way MSN is encroaching on our lives :lol:
[8125, K-JAM, P4300, MDA Vario General] mattucd:
He's pretty unstable, always mumbling to himself...I'm afraid he might try to off me further down the road :shock:
[8125, K-JAM, P4300, MDA Vario General] emugpp:
I can't believe it, I just read this topic..I never got HitchHiker to work..now I simply registered my pocket msn, and hichthiker connected! without a soft-rest or anything HitchHiker depends on pocket MSN!? its unbelievable.

I always loved the simplicity of the prog, but after connecting acociating etc, the connection was lost. Just register your MSN and the damn program works..VERY strange!
[Wear OS Q&A, Help & Troubleshooting] flasd:
I know the iPod Nano 6g can't connect to a phone through WiFi nor Bluetooth but there is any way to port the Android Wear to it?
[Wear OS Q&A, Help & Troubleshooting] falco66:
I do not think
[Wear OS Q&A, Help & Troubleshooting] rharshit:
NO. iPOD is different platform. And android is opensource. You can make it work on an android smart watch. But not on iPOD

And moreover, even if you make it, how are you gonna flash it?
[Wear OS Q&A, Help & Troubleshooting] DirtDigler:
yes
[Wear OS Q&A, Help & Troubleshooting] lloyd06:
no i think no one can port that
[Wear OS Q&A, Help & Troubleshooting] thesparky007:
Why do people even ask these questions
[Wear OS Q&A, Help & Troubleshooting] mikereidis:
Because they don't know the answers ? ;)

Not everyone has dev/porting knowledge.

As for the question, in theory anything is possible. In practice nobody's going to do a major reverse engineering job for something like this, even in the remote chance it was possible, or even desirable.
[Wear OS Q&A, Help & Troubleshooting] KratosTheSpartan1990:
i doubt you can, as apple has always been very unhelpful when it comes to compatibility with android, and, as someone else already stated, you have no way of flashing it on an ipod.
[Wear OS Q&A, Help & Troubleshooting] hiepgabacninh:
,...............
[Wear OS Q&A, Help & Troubleshooting] theonlyanil:
It would have been awesome if Android wear could be ported to iPod nano. I own an iPod nano + a lunatik watch case. But as on date, it has become useless because fitness data cannot be synced to nike website anymore. :/
[Galaxy S II Q&A, Help & Troubleshooting] Ultrasagol:
After making a stupid step wiping my phone data, it stucks on Samsung boot logo and nothing further.

Recovery is not accessible but I can boot to download mode with 3-key-combo.

I'm trying to go back to stock firmware with Odin but it keeps failing.

<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100JHLS7_I9100PTRLS4_I9100JHLS2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> [B]Complete(Write) operation failed.[/B]
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.

I made sure no KIES tasks on, ran Odin as Administrator as well.

So far I tried multiple USB ports and various cables. Also tried Odin 3.4, 1.8, 1.3...

On 1.8 and 1.3 Odin is just stuck in "SetupConnection..."

Any ideas?
[Galaxy S II Q&A, Help & Troubleshooting] doctor_droid:
Make sure u have proper usb drivers on ur pc.. reinstall them and retry
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Make sure you find Hopper8's 'Odin troubleshooting' thread stickied in General & try everything in that thread as many times as you need to in order to get a successful flash, these things are almost always fixed with perseverance. If you don't persevere, your phone stays busted.

Don't try 5 or 6 things, come back to this thread & say 'It doesn't work' because there is nothing that isn't in that thread that can be suggested in these situations, every single possible thing you've missed & every little thing you can try is in that thread in one place.
[T-Mobile Samsung Galaxy S 4] xologist:
Hey guys..

My phone is stuck at the "Samsung Galaxy S4" screen" where it shows just the letters.

The last thing I remember doing was using taskiller and phone's memory killer to kill memory because it was slow... and when I tried to open up text messages, it wouldn't open.

So I restarted the phone and now it's stuck at the "Samsung Galaxy S4" Screen.

( I also removed some apps days before.. but I had rebooted and phone it was working just fine).

- I haven't tried to reinstall a radio.. I woudn't know which one.

- I can access odin just fine by clicking the 3 keys.

- I Can't access TWRP Recovery. I held the 3 keys, and it shows the message on the left corner like it's going to go, but then just reboots and gets stuck on samsung screen.

Tried to reinstall it, but didn't seem to work I guess.. since it still shows the left corner message, but doesnt go to twrp.

Details about my phone:

SGS4 Rooted.

Rom, Custom Stock Rom.. Jedi S4X ( URL of ROM http://xdaforums.com/showthread.php?t=2331942 )

What Can I do?

I dont care what I have to install/remove, but I have very important things on the phone that I CANT have deleted!

HELP ME ??
[T-Mobile Samsung Galaxy S 4] Corwinder:
Can you reflash the recovery using Odin? If so do that and if necessary reinstall the room your running.

---------- Post added at 09:24 PM ---------- Previous post was at 09:24 PM ----------

Rom dam keyboard
[T-Mobile Samsung Galaxy S 4] xologist:
Recovery did not want to install!

Just got it back working, and I am about to do as you say.

will keep posted
[T-Mobile Samsung Galaxy S 4] xologist:
I keep installing the rom, but it doesn't work.

I keep getting stuck at the "samsung Galaxy screen"
[T-Mobile Samsung Galaxy S 4] Kriptik210:
When you boot into TWRP, hold the 3 keys and when you feel the phone vibrate, let go of the power key and remain holding Vol down and home key until the boot screen pops up.

Let me know if this worked

Sent from an A.I. frequency
[T-Mobile Samsung Galaxy S 4] bobolinko:
Boot into Recovery - ( turn off the phone, then hold volume up and press power so it goes on.)

Then when the small blue word comes on at the top left of the screen, let go of the volume button.

when the recovery menu comes up, scroll using the volume button to find

factory reset

.

when you see that, press the power button once. the phone will boot and do some things and hopefully it will boot up again.

It should be just like when you turned the phone for the first time when it was brand new.

You will have to install any apps you had installed. Do not worry, if you paid for any apps, you can download them again without paying again.

let us know if this helps!

Good Luck and Aloha!
[T-Mobile Samsung Galaxy S 4] nivekx9:
If above doesn't work... Odin stock.
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
Out of curiosity, why are you holding power+HOME+volume up/down? Just wanted to throw it in there that there is no need to hold the home button when accessing recovery or download mode. Simply pressing Power+Volume up/down should be sufficient. Also, as someone else pointed out, just release power when you feel the vibrate and once you see "Recovery booting" in the top left-hand corner, let go of the volume key.

Also, if you're still unable to access recovery after all that; I'd recommend using Odin to flash the stock image, boot up, then use Odin to flash whatever recovery you want.
[Verizon Samsung Galaxy S 4] thecityboy781:
i got root access using the saferoot app thing, so once i download safestrap and reboot to recovery it goes straight to D/L mode anyone know why?
[Verizon Samsung Galaxy S 4] DaGamer12345:
Booting into recovery from the power menu is not supported. Either reboot and press the Menu button when the Safestrap splash screen comes up or use the Safestrap app to boot into Safestrap.
[Verizon Samsung Galaxy S 4] thecityboy781:
i select 'reboot to recovery' within the app and it just reboots my phone
[Verizon Samsung Galaxy S 4] DaGamer12345:
Then when the Safestrap splash screen comes up press the Menu button to go into recovery. If it doesn't come up at all, make sure you installed the recovery correctly and not just the app.
[Verizon Samsung Galaxy S 4] thecityboy781:
ahhh, that explains it cause i just downloaded the APK
[Verizon Samsung Galaxy S 4] Mistertac:
Yea... You have to actually install the recovery.
[Verizon Samsung Galaxy S 4] thecityboy781:
and how i do that cause i watched a youtube video and the dude said to do that and it didn't work any help would be greatly thanked =]
[Verizon Samsung Galaxy S 4] decaturbob:
ok...installing safestrap is a 2 step process:

1. step one is to install the actual safestrap APK program

2. step two is to open safestrap program up and install the recovery.

then using your power off button to restart your phone, the safestrap splash screen will come up...hit the actual button (menu) to go into safestrap recovery, not the screen icon button.

please review the following thread before doing anything else to your phone

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