Related
Hey guys,
So I've got a rooted Nexus 4 and it does not have any custom ROM installed. I'm running the stock OS and it's smooth and functions without any problems. The battery life of the device is okay but I would definitely like it to be more efficient. The franco.kernel is praised all over the web, especially here at XDA and I definitely want to use it. I'm wondering what the easiest way to flash it on there would be. I've seen that fastboot
is one way to do it but I'm not sure on how to do that. Any help is appreciated Also, is any sort of wipe involved when flashing a kernel? Backing up is a mission and I've had terrible experiences restoring any backed up data so if avoiding one is possible, that'd be great. Thanks in advance!
All you have to do is flash it in recovery. Wiping cache won't do any harm either.
When I also just got my N4, the first thing I did was flash franco.Kernel because I didn't know better. It's definitely not the best kernel out if you look at our section. My favorite kernel is Trinity Four. Battery life is great, the thread atmosphere is awesome (we don't just talk about the kernel. Take a look and see) and the kernel is super stable.
Sent from my Nexus 4 using xda premium
android88 said:
All you have to do is flash it in recovery. Wiping cache won't do any harm either.
When I also just got my N4, the first thing I did was flash franco.Kernel because I didn't know better. It's definitely not the best kernel out if you look at our section. My favorite kernel is Trinity Four. Battery life is great, the thread atmosphere is awesome (we don't just talk about the kernel. Take a look and see) and the kernel is super stable.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I beg to differ. Franco's kernel has been the best in my opinion. I have tried all kinds of kernels and they were either hot or a battery hog. Franco's kernel is the most ideal for me
Everyone has a subjective opinion on every kernel so it depends on you.
Sent from my Nexus 4 using Tapatalk 2
Thanks for the replies guys! My most primary concern is battery life. I doubt I'll be using the kernel for anything else really. Any idea on how long it takes for a kernel to be fully stable and release with updates once in a while? I know a lot of people like one of Franco's builds specifically, which is a nightly.
I think trinity kernel is one of the best out there and very stable and updates are very fast.
YeezyMode said:
Thanks for the replies guys! My most primary concern is battery life. I doubt I'll be using the kernel for anything else really. Any idea on how long it takes for a kernel to be fully stable and release with updates once in a while? I know a lot of people like one of Franco's builds specifically, which is a nightly.
Click to expand...
Click to collapse
If your looking for battery life , def give Fauxs a look, he has a special eco mode if you want epic battery life
YeezyMode said:
Thanks for the replies guys! My most primary concern is battery life. I doubt I'll be using the kernel for anything else really. Any idea on how long it takes for a kernel to be fully stable and release with updates once in a while? I know a lot of people like one of Franco's builds specifically, which is a nightly.
Click to expand...
Click to collapse
Well, I think most of the kernels available are pretty stable. I haven't had any RR's/SOD's. Trinity is also updated pretty often.
Sent from my Nexus 4 using xda premium
Check the trinity thread . . its just been updated with latest colours
Sent from my Nexus 4 using Tapatalk 2
Cool :good: , checking out the Trinity thread and exploring Franco/Fauxs as well. Thanks everyone
I've been using Franco kernel with stock rom since I got a Nexus.
I love this combo and have yet to see any stability problems.
diablos991 said:
I've been using Franco kernel with stock rom since I got a Nexus.
I love this combo and have yet to see any stability problems.
Click to expand...
Click to collapse
Hey! Which version are you using? Also, do you find that the Play Store updater is necessary?
This time around I have just been using the stable releases. R53 is what I am using right now.
I don't play with the voltages or anything, just flash the .zip and use as normal. With all my android phones, instability happens when playing with the under-voltage settings. It just isn't worth it to me to squeeze out that extra 20 minutes of battery life.
I would only use the play store app if I planned on messing with the colors or regularly flashing nightlies.
diablos991 said:
This time around I have just been using the stable releases. R53 is what I am using right now.
I don't play with the voltages or anything, just flash the .zip and use as normal. With all my android phones, instability happens when playing with the under-voltage settings. It just isn't worth it to me to squeeze out that extra 20 minutes of battery life.
I would only use the play store app if I planned on messing with the colors or regularly flashing nightlies.
Click to expand...
Click to collapse
Thank you very much, I'll probably flash r53 tonight and see how things go after a few days of use I bought Franco's Display Control app so I'm pretty sure I won't be needing the updater for colour controls
You don't need to wipe anything before flashing Franco's kernel. Wiping cache/dalvik isn't needed (that's a ROM thing add opposed to a kernel thing).
Sent from my Nexus 4 using xda premium
steviewevie said:
You don't need to wipe anything before flashing Franco's kernel. Wiping cache/dalvik isn't needed (that's a ROM thing add opposed to a kernel thing).
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Ah okay good to know, thanks!
I used franco's kernel over the past weeks but I many wakelocks. Then I tried harsh's and got average (kernel!) wakelocks at 1-1.5%. I UV so my phone is pretty colder compared to franco's. With faux's I could make me some bacon
Sent from my Nexus 4 using xda app-developers app
Hey so I'm hoping someone here can help. I did an nandroid backup on my phone, then flashed franco's kernel. My phone will not turn on anymore, every time I try to hold the power button down or boot into bootloader, the LED just flashes red.
Am I screwed?
SSD4130 said:
Hey so I'm hoping someone here can help. I did an nandroid backup on my phone, then flashed franco's kernel. My phone will not turn on anymore, every time I try to hold the power button down or boot into bootloader, the LED just flashes red.
Am I screwed?
Click to expand...
Click to collapse
You're probably going to be better off asking that in this thread: http://forum.xda-developers.com/showthread.php?t=2002782
SSD4130 said:
Hey so I'm hoping someone here can help. I did an nandroid backup on my phone, then flashed franco's kernel. My phone will not turn on anymore, every time I try to hold the power button down or boot into bootloader, the LED just flashes red.
Am I screwed?
Click to expand...
Click to collapse
The kernel isn't the problem. What you have to do is remove the battery and plug it back in. It's as easy as that.
I somehow got it back working without opening the device.
Try to long press the power button or the power button and volume down.
Sent from my Nexus 4 using xda app-developers app
For my surprise today my phone don't respond, I left charging with the travel adapter, no boot, no Samsung logo, no recovery no download mode, maybe Is a sudden death problem :'(
I put my battery in the my wife's S3, and the battery is fully charged.
This is my last configuration:
Wanamlite rom 6.0
Philz touch recovery 4.63
Stock kernel (rom's kernel)
Last bootloader with the red light I in the upper left corner.
Enviado desde mi E15a usando Tapatalk 2
You should have been protected from Phil recovery perhaps that line of kernel code doesn't fix SDS after all.
Sent from my GT-I9300 using xda premium
no, philz recovery would only protect him while he was in the recovery
delsus said:
You should have been protected from Phil recovery perhaps that line of kernel code doesn't fix SDS after all.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
So? what went wrong Mr. delsus?
This is very concerning but let's not jump to conclusions too fast, shall we? People would freak out.
Maybe someone can look over the leaked kernel and search for the SDS string (Movi ops or something ).
Sent from my GT-I9300 using Tapatalk 2
No source, no strings... They said. (I already asked)
Sent from my GT-I9300 using xda premium
Glebun said:
no, philz recovery would only protect him while he was in the recovery
Click to expand...
Click to collapse
Makes sense, so the real need for the fix in recovery isn't really needed, the chances of SDS in recovery are almost none existent.
Sent from my GT-I9300 using xda premium
delsus said:
Makes sense, so the real need for the fix in recovery isn't really needed, the chances of SDS in recovery are almost none existent.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Of course they are existent... What if you are running a Nandroid Backup or you're installing a new ROM...
Those two activities take more I/O Requests to the memory chip than the "Normal" usage of the phone, you are reading and writting to the memory like crazy...
So the recovery fix is completely needed my friend...
jimbo77 said:
Of course they are existent... What if you are running a Nandroid Backup or you're installing a new ROM...
Those two activities take more I/O Requests to the memory chip than the "Normal" usage of the phone, you are reading and writting to the memory like crazy...
So the recovery fix is completely needed my friend...
Click to expand...
Click to collapse
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Must.... flash..... back..... to.... sds....safe....romm...
Oh wait, warranty .
Sent from my GT-I9300 using xda premium
How old was your phone? Are you sure your memory wasn't damaged enough before the fixes got launched?
I can't figure out why Samsung shouldn't fix it for that 4.2.1 build. Maybe to screw leakers?
Sent from my GT-I9300 using xda app-developers app
delsus said:
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
But Jimbo is correct - we don't know what causes the SDS but there is a very real possibility of a higher risk on more intensive IO operations.
This does not depend on time but rather on the wear of the EMMC, it has been theorized that the wear leveler is again at fault (like on S2 superbrick)
Recovery and restore are maybe the most intensive IO operations (besides installing AND the transcoding - which is seemingly done while charging, remember the Video Player CPU usage on that state... maybe that's the reason why it manifested... but I cannot tell for sure).
htcsnap93 said:
Must.... flash..... back..... to.... sds....safe....romm...
Oh wait, warranty .
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
LOL !!!
so what about someone unpacking the kernel and find if this lines r in drivers/mmc/core/mmc.c and mmc_ops.c
https://github.com/AndreiLux/Perseus-S3/commit/54ddcbe7aff1c19c07f76a05ab45f37bcbae2951
t0n0n said:
How old was your phone? Are you sure your memory wasn't damaged enough before the fixes got launched?
I can't figure out why Samsung shouldn't fix it for that 4.2.1 build. Maybe to screw leakers?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Now you speak of memory, comes to my mind that this rom has a swap memory partition, if you type "free" on the terminal emulator, you can see it.
I bought the phone on june 1, 2012.
delsus said:
The majority of reports of SDS are whilst they are charging, also unless you flash more than 4 times a day you don't spend much time in recovery.
I haven't seen anything to say the amount of read/write requests affect SDS, its not the only thing that can make your NAND fail.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Exactly. It is the correlation between charging and SDS which is quite apparent when analyzing the data thread that has led me to speculate that the factory charger may be responsible for this, or at the very least be exacerbating the situation. I've never used the stock charger, (mine is still in the box and I'm using the SII charger) but there are several reports of fried USB cables, etc. when using the stock charger, so I don't think it too far-fetched that they could be related somehow.
donalgodon said:
Exactly. It is the correlation between charging and SDS which is quite apparent when analyzing the data thread that has led me to speculate that the factory charger may be responsible for this, or at the very least be exacerbating the situation. I've never used the stock charger, (mine is still in the box and I'm using the SII charger) but there are several reports of fried USB cables, etc. when using the stock charger, so I don't think it too far-fetched that they could be related somehow.
Click to expand...
Click to collapse
stock charger has nothing to do with SDS its bug in the eMMC firmware :silly:
they would've issued a statement about it it though, because it would've saved a lot of phones
yahyoh said:
stock charger has nothing to do with SDS its bug in the eMMC firmware :silly:
Click to expand...
Click to collapse
Yup, the thing is, apparently there is a TranscodeService for the Video Player that is triggered to start on charge, the operation should be IO intensive. That could be a valid co-relation. But the charger itself does not have any influence from what developers have gathered, it is a defect in the eMMC firmware.
This is really an great discussion
I wanted to know if I flash with any other kernel instead of stock, will there be even problem on leak
Sent from my GT-I9300 using xda app-developers app
I had Franco's 110, then flashed Faux's kernel resetter and Motley's 37 one after another. Phone now would not turn on. I searched other threads and it seems like holding vol + and - together with Power, should fix it. However in my case,only the led turns on and stays solid red.
Any ideas?
Check and make sure you didn't flash a Nexus 7 kernel version.
If you did its toast.
Sent from my Nexus 4 using xda premium
Rest in peace if n7 kernel..
The Kernel file name is motley_422_n4_exp_build_37
However, Kernel resetter was downloaded from N7 thread, for some reason I was under impression its the same file...
The file name is grouper-faux123-reset-kernel-4.2.2
moldovanos said:
However, Kernel resetter was downloaded from N7 thread, for some reason I was under impression its the same file...
The file name is grouper-faux123-reset-kernel-4.2.2
Click to expand...
Click to collapse
Kernel resetter is just the stock kernel. If you got it from the N7 forum its the N7 stock kernel.
Sorry.
Sent from my Nexus 4 using xda premium
You can't even boot to the bootloader ?
Farewell Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
Never rooting the Nexus if i get it, such a fragile phone...
abdi7451 said:
Never rooting the Nexus if i get it, such a fragile phone...
Click to expand...
Click to collapse
Hi,
This is not the phone that is fragile, it's what the user do with it... If you flash a kernel from a Nexus 7 to the Nexus 4... for me it's legitim to have "a little problem"... It's the same thing for all the phones, try to flash a kernel from another phone instead the one make for your phone and see the result...
If you don't read correctly and don't paid attention at what you do or flash... It's not the phone that is the responsible...
viking37 said:
Hi,
This is not the phone that is fragile, it's what the user do with it... If you flash a kernel from a Nexus 7 for the Nexus 4... for me it's legitim to have "a little problem"... It's the same thing for all the phones, try to flash a kernel from another phone instead the one make for your phone and see the result...
If you don't read correctly and don't paid attention at what you do or flash... It's not the phone that is the responsible...
Click to expand...
Click to collapse
Yea, but a lot of people have been having problems with the infamous "Red light of death" after simply rooting, or letting the phone battery completely deplete itself. I'm still gonna get this phone, but I'm kinda cautious. Does it come with a warranty from Google?
abdi7451 said:
Yea, but a lot of people have been having problems with the infamous "Red light of death" after simply rooting, or letting the phone battery completely deplete itself. I'm still gonna get this phone, but I'm kinda cautious. Does it come with a warranty from Google?
Click to expand...
Click to collapse
This issue and the battery issue you are referring to aren't related.
The N4 led just flashed red when there is an error. It could be a variety of things.
Sent from my Nexus 4 using xda premium
El Daddy said:
This issue and the battery issue you are referring to aren't related.
The N4 led just flashed red when there is an error. It could be a variety of things.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Has it happened to you?
abdi7451 said:
Has it happened to you?
Click to expand...
Click to collapse
No. I don't do things to my phone that cause problems.
Sent from my Nexus 4 using xda premium
abdi7451 said:
Yea, but a lot of people have been having problems with the infamous "Red light of death" after simply rooting, or letting the phone battery completely deplete itself. I'm still gonna get this phone, but I'm kinda cautious. Does it come with a warranty from Google?
Click to expand...
Click to collapse
You bought a Nexus device. Use it. Root it. Flash it. Play with it. You worry too much. Stop being so paranoid. Again, if you carefully do the correct steps you will get the results you desire. If you miss a step you will be sad that you screwed up your phone. If you're in math class and you miss a step to the formula to the equation you will get it all wrong. Pay attention to all the little details. You will be a pro at rooting in the future if you follow the steps meticulously.
Sent from my Nexus 4 using Tapatalk 2
So...as I understand I should just throw it in the garbage now?
scream4cheese said:
You bought a Nexus device. Use it. Root it. Flash it. Play with it. You worry too much. Stop being so paranoid. Again, if you carefully do the correct steps you will get the results you desire. If you miss a step you will be sad that you screwed up your phone. If you're in math class and you miss a step to the formula to the equation you will get it all wrong. Pay attention to all the little details. You will be a pro at rooting in the future if you follow the steps meticulously.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So everyone with the red light of death is an idiot that didn't follow the steps?
moldovanos said:
So...as I understand I should just throw it in the garbage now?
Click to expand...
Click to collapse
It may be able to be repaired. Here's the same problem from the other day.
http://forum.xda-developers.com/showthread.php?t=2208312
There is a link to a JTAG service in that thread.
Sent from my Nexus 4 using xda premium
have you tried flashing the factory image via fastboot? can you get into the bootloader?
El Daddy said:
It may be able to be repaired. Here's the same problem from the other day.
http://forum.xda-developers.com/showthread.php?t=2208312
There is a link to a JTAG service in that thread.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
thank you, I guess thats the only option left
simms22 said:
have you tried flashing the factory image via fastboot? can you get into the bootloader?
Click to expand...
Click to collapse
nope, I just can make the Led flash for a quick second:crying:
abdi7451 said:
Never rooting the Nexus if i get it, such a fragile phone...
Click to expand...
Click to collapse
yeah not fragile at all. people don't know what they are doing (no offense guys). they just need to READ everything. the stickies at the top of the forums explain everything in detail. flashing a kernel for a completely different device is just asinine. as long as people arent stupid about things, fastboot can always save their asses.
---------- Post added at 11:10 AM ---------- Previous post was at 11:06 AM ----------
abdi7451 said:
So everyone with the red light of death is an idiot that didn't follow the steps?
Click to expand...
Click to collapse
im guessing so. i had the "red light of death" last night. i was using my phone at like 2% battery left, rebooted it and it said i had 5% left. big whoop my battery calibration is a little jacked. well i kept using it and instead of going through the shutting down thing when the battery died, the screen just went blank. again, because the battery calibration is way off. so i plug it in, and the light turns red for about 10 seconds. then the light turns off, and the battery charging icon appeared. i waited 10 mins for it to get a small charge then booted right up. not a single problem. i really dont get why everyone is having such freak accidents and problems with this phone.
I'm super excited that it finally came in the mail. Whats the first thing I should do to, or with it?
Don't be shy you guys, throw some ideas at me.
For a root, I'm thinking cm10.1 (Should I leave the kernal or change it?)
Best nexus 4 feature? Or any cool things about the phone that would take me a month to figure out on my own?
Read.
Enviado desde mi Nexus 4 usando Tapatalk
Check for damages after opening the box
Sent from my Nexus 4 using xda premium
I'd recommend leaving stock rom, unlock, root, and install franco kernel. Go into settings, about phone, repeatedly tap Android version, and a smiling jellybean will pop up.
Sent from my Nexus 4 using Tapatalk 2
re4lsk said:
Read.
Enviado desde mi Nexus 4 usando Tapatalk
Click to expand...
Click to collapse
Hmm, didn't think to do that. I'm going to read it now. Thank you for the advice!
davidang said:
Check for damages after opening the box
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I checked, mine was fine upon arrival. Did you have a different experience?
UnlockedNand said:
I'd recommend leaving stock rom, unlock, root, and install franco kernel. Go into settings, about phone, repeatedly tap Android version, and a smiling jellybean will pop up.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I unlocked it. Thank you for suggesting the franco kernel. I think I read somewhere that the franco kernel with cm10 was brilliant. I would leave it stock, but I feel like I've gotten to know the phone quite well already lol. I haven't played the jelly bean game yet btw. Good tip.
Definitely throw on Franco's kernel. If you also get his kernel updater app, I would recommend changing your screen gamma settings to match this post http://forum.xda-developers.com/showthread.php?p=39012344#post39012344. I brought down the red a little bit because I like my colors to be a little cooler . I personally think this is the way our screen colors should have been calibrated all along as it looks so much better.
AW: [Q] Just got my Nexus4!!!
But with that Kernel I wont recieve OTA updates anymore right ?! So how to update later ?
Sent from my Nexus 4 using xda app-developers app
check the battery life, and download some games to check its performance, and also in taking pics or audio. anyway, just the respect you are concerned.
post in the correct section
First thing is download the factory image from Google so you have it to hand should you need to go back to stock. Also make sure you know adb/fastboot commands and don't use toolkits (they're for the lazy). Make sure you understand how to reboot the unit should something go wrong and generally read every guide you can on here before doing anything
EddyOS said:
First thing is download the factory image from Google so you have it to hand should you need to go back to stock. Also make sure you know adb/fastboot commands and don't use toolkits (they're for the lazy). Make sure you understand how to reboot the unit should something go wrong and generally read every guide you can on here before doing anything
Click to expand...
Click to collapse
Finally, some good advice. I'd also recommend creating a nandroid in recovery BEFORE flashing anything. It might be a good idea to save a copy on your computer. Could save you some hassle later.
EddyOS said:
First thing is download the factory image from Google so you have it to hand should you need to go back to stock. Also make sure you know adb/fastboot commands and don't use toolkits (they're for the lazy). Make sure you understand how to reboot the unit should something go wrong and generally read every guide you can on here before doing anything
Click to expand...
Click to collapse
I should have took your advice. I bricked my phone :/
In my defense it was at 6 in the morning after a long and stressful night at work. Very depressing.
Also, would you mind if I stole your signature? lol
Alpha-Wat3rloo said:
I should have took your advice. I bricked my phone :/
In my defense it was at 6 in the morning after a long and stressful night at work. Very depressing.
Also, would you mind if I stole your signature? lol
Click to expand...
Click to collapse
How did you brick it? Wrong ROM/kernel?
Sent from my Nexus 4
I replied to you in my other Q&A post.
HI i bought it 2days ago night and rooted yesterday battery life is INCRIDBLE at least SOOO MUCH BETTER THAn my old s4 DD btw do ur ecommend me to do it? as its factory clock at a factory voltage hmm... why didnt google do it at first?? is it risky
oh and i dont like to flash custom kernel(( can i do it whitout a kenrel???:|||
czoz kernel fast charge and stuff make me worri and i lvoe stuck many things!!!
As long as I know you can't undervolt without a custom kernel.
An why would you want to undervolt if your battery is already amazing ?
Sent from my Nexus 4 using xda app-developers app
failly said:
As long as I know you can't undervolt without a custom kernel.
An why would you want to undervolt if your battery is already amazing ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
well always mroe abttery great u right i will jsut try to see if i get battery problems in outside coz here no stress if battery low i jsut connect to power btw i always carried the cable and power whit me everywhere on s4
kamranhaghighi said:
well always mroe abttery great u right i will jsut try to see if i get battery problems in outside coz here no stress if battery low i jsut connect to power btw i always carried the cable and power whit me everywhere on s4
Click to expand...
Click to collapse
See, no problem!
And if you need more battery in the future you can always flash a custom kernel and undervolt!
Sent from my Nexus 4 using xda app-developers app
failly said:
See, no problem!
And if you need more battery in the future you can always flash a custom kernel and undervolt!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
ok ty no risks? and no downsides of a custom kernel? if i wanted to do
kamranhaghighi said:
ok ty no risks? and no downsides of a custom kernel? if i wanted to do
Click to expand...
Click to collapse
I don't know, just make sure to read the instructions. I don't have a custom kernel installed so I don't really know!
Sent from my Nexus 4 using xda app-developers app
The risk of undervolting is not giving it enough power and setting that on boot so you end up not being able to get into android. Meaning you would have to flash a stock kernel with fastboot.
You only risk damage to the hardware if you overclock. That raises the operating temperature of the cpu, and thus could shorten the overall lifespan.
The risk to running a custom kernel is the same risk of running any experimental software: there could be bugs.
And of course the factory clock speed is set at the factory voltage... it just came from the factory....
And asking why Google doesn't include the option is akin to asking why it isn't rooted outta the box
xD ok i will probably do if i had then but i just dont wonna lose that awesome nexus feeling and stuff! anyway ur profile pic gave me a heart attack seems not gonna make it bad
I don't see much difference in battery life but I definitely feel a difference in heat which imo is important. I dont find myself worrying about anything happening to my n4 anymore because they're so cheap now a days that I can just buy another one or wait for the 13 version.
My phone rarely goes over 100°f
Sent by flying midget