Related
Hi,
I noticed, that after a total standstill, there is now a little movement on the nike android front. I want to contribute a little share to that.
I have set up an autobuild service for the android kernel. I automatically uploads a fresh zImage with the newest patches every full hour. I also reenabled Vibration as I never had any problems with that. If there are still people aound that need a kernel without Vibration let me know, I could set up a second build, too.
[update 03.03.10] Kernel without vibration for niki100 included.
The fresh kernel is found here.
[2010.03.31]UPDATE:
- IRQ wakeups enabled -> sleepmode 1 works
- Red led flashes when sleeping
- hw3d for eclair can be chosen in commandline (not fully functional)
- Double press cam button is home on 20key nike now
[2010.04.08]UPDATE:
- Some Keypad and defconfig changes to support ubuntu
[2010.07.01]UPDATE:
- Added .patch files to downloads for all who want to compile on their own (Recommanded! Some new devs would be very welcome here)
[2010.07.02]UPDATE:
- Removed .patch files again, they don't work as intended. Just 'git apply' the "Changes compared to stock kernel" instead...
- Fixed audio (please give me some feedback if it works now)
[2010.08.30]UPDATE:
- I just was tipped of that the service has been down for full 3 months (thx youngsien)
- Service is now online again, but will from now on only be updated once a day (should be enough)
Happy Androiding everyone!
mblaster
PS: If you don't know what a zImage is or does: It is the core of the Android operating system. It is usually in the same folder like haret.exe. You can tell your Android build to use a specific zImage in default.txt
Nice idea...
That's what we need to make good android builds working on nike.
The vibration ALLWAYS freezes de touchscreen, maybe a htc p5500 model issue.
i will follow this post hourly...
OK, I included the stock kernel without vibration in the service. Have fun!
@arleybarros: I dind't mean to post here hourly, but my server will keep the kernel up to date
the stock kernel freezes after a little vibration..
shouldn't vibration be disabled on stock release?
nik2208 said:
the stock kernel freezes after a little vibration..
shouldn't vibration be disabled on stock release?
Click to expand...
Click to collapse
Yeah, you're right. The files were exchanged by my build script... Thanks for the hint, everything should be fine now.
*bump*
New updates in first post... I hope everything works
mblaster,could you post your default.txt cmdline, please? seems like nike still does not sleep, there no signs of flashing red led on mine.
my cmdline: "pm.sleep_mode=1 mddi.width=320 mddi.height=480 hw3d.version=1"
I'm running msmissions eclair.
are you running it without rootfs? there seems to be a problem with the norootfs basefiles that prevents sleeping.
yup, norootfs.
ok, got progress, I've runned android again, now nike felt asleep and flashing red led. wakeup works too - double tap on dpad center. I think that was because there was no reboot after installing after data wipe, norootfs missing some controls on power.
also, there is another power problem - MSM's standard reboot/poweroff commands from android does not working, can we fix this? device just freezing, seems like some revision on vogue's power controlls broken ours.
rzk333 said:
also, there is another power problem - MSM's standard reboot/poweroff commands from android does not working, can we fix this? device just freezing, seems like some revision on vogue's power controlls broken ours.
Click to expand...
Click to collapse
The same here with the norootfs stuff. I tried myn's donut on sqsh and norootfs. SQSH works like a charm (powermanegement, net, reboot, powerdown), but the same build/kernel combination has the problems mentioned before...
[minor UPDATE] Double press cam is home now on 20key nike
here is that someone is going to operate the headphones??
i can't use internet.
help me.
i set my carrier.but i can't use internet
[minor UPDATE] Double press cam is home now on 20key nike
Click to expand...
Click to collapse
can we make something about "Enter" key on niki100?
I've tried to run kaiser ubuntu and stuck with login - I simply cannot press enter :/
maybe some virtual button can be mapped to something?
rzk333 said:
can we make something about "Enter" key on niki100?
I've tried to run kaiser ubuntu and stuck with login - I simply cannot press enter :/
maybe some virtual button can be mapped to something?
Click to expand...
Click to collapse
Where would you like to have the enter key? I can try to fix it in, but i am not sure where to put it.
Some ideas would be:
- Put enter on cam, press WinKey once = menu, press Winkey twice = home
- Put enter un the key on the lower right (InternetExplorer in winmo?), probably better, but i dont know for shure which button it is. Dou you get a 'z' if you press it? I guess you do:
Code:
{{KEY_Z,FALSE,FALSE,FALSE,FALSE},FALSE}, // UNKNOWN KEY
Can you confirm that you get a 'z'? I will change it to enter then.
€: If ubuntu works it would be nice if you could start a thread about it. Would be great to have a full blown linux box in your pocket
Latest Kernel is working nicely on my Nike100, really impressed with the battery life now, great job on getting sleep to work. I have a request though... would it be possible to make one more kernel for the Nike 16 key? at the moment you can't type on it or use any of the keypad as the mappings are all wrong. If it would help I can tell you what keys are currently mapped to what on the 16 key. I don't know how hard it would be to change but if it is doable I would really appreciate it as it is really the last thing that is stopping the port from being day to day usable for me and other 16 key users. Unfortunately the onscreen keypad is just a bit small for typing with daily.
Thanks, hope its not too hard a fix.
MWG_Thomas said:
Latest Kernel is working nicely on my Nike100, really impressed with the battery life now, great job on getting sleep to work. I have a request though... would it be possible to make one more kernel for the Nike 16 key? at the moment you can't type on it or use any of the keypad as the mappings are all wrong. If it would help I can tell you what keys are currently mapped to what on the 16 key. I don't know how hard it would be to change but if it is doable I would really appreciate it as it is really the last thing that is stopping the port from being day to day usable for me and other 16 key users. Unfortunately the onscreen keypad is just a bit small for typing with daily.
Thanks, hope its not too hard a fix.
Click to expand...
Click to collapse
Do you have this parameter in default.txt?
Code:
board-htcnike-keypad.keypadlayout=1
If not, add it and remove other entries concerning keypad layouts (might be there from kaiser). Most of the keys should be mapped correctly. Enter key seems to be missing. Could you try to press the button on the lower right (Internet explorer or something like that, depending on the branding of your phone) and tell me if it prints the letter 'z'?
Where would you like to have the enter key?
Click to expand...
Click to collapse
iexplorer key is useless in ubuntu and android, I think, so we can remap it, camera home key is used widely in android, you dont need to open up slider to access menus
If ubuntu works it would be nice if you could start a thread about it.
Click to expand...
Click to collapse
that would be nice too, now we can run LXDE or other X windowmanager compiled for ARM, ubuntu boots up fine and works like on kaiser. you can learn how this happen for ARM in Omegamoon's blog
The patched kernels will be ready on my download page in a few minutes (compiling...). Please let me know if it worked.
Hi all, I am wondering if anyone knows how I can disable the touch capacitive buttons on the flyer/view.
I use my tablet in landscape a lot, and end up using the bezel as a handle and then hit the buttons, I am running DextersJB14 rom with the patch.
Any help would be appreciated.
Hm, strange enough, at the moment I use DextersJB16 and these buttons are not active. I used 14, 13 and 12 and cannot even remember the buttons were active... Did you look through dev settings?
i believe he is running mobileUI edition and i activated buttons here, and a fault in the wifi build.prop also enables the softnav buttons.
if the build.prop is modified , the hardware buttons remain active (as many requested for mobileUI) and softbuttons goes away.
it will be fixed so softbuttons are gone in next update, hardware buttons remain active in mobileUI
PabloFiasko said:
Hm, strange enough, at the moment I use DextersJB16 and these buttons are not active. I used 14, 13 and 12 and cannot even remember the buttons were active... Did you look through dev settings?
Click to expand...
Click to collapse
Interestingly enough, the buttons are not lit, but do respond. I didn't see any settings that appeared to be able to change this. Might be nice to make this a toggle setting in the future, though I don't know what that would entail for Dexter. I suppose I could try out 16, didn't realize it was out.
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
HellRazorGod said:
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
Click to expand...
Click to collapse
You'll be hard pressed to find a 4.2.2 ROM that doesn't have some sort of on-screen control. Do a bit of searching around on XDA of all the 4.2.2 ROMs, look at screenshots etc. Navigation bar is the same style as a Nexus 4. Pie controls are a method of on-screen control. AOKP ribbons are also for on screen control. There's probably more. Then there exist ROM's which attempt to mimic the AOSP, Nexus-style experience. Plenty to choose from.
Hopper8 said:
You'll be hard pressed to find a 4.2.2 ROM that doesn't have some sort of on-screen control. Do a bit of searching around on XDA of all the 4.2.2 ROMs, look at screenshots etc. Navigation bar is the same style as a Nexus 4. Pie controls are a method of on-screen control. AOKP ribbons are also for on screen control. There's probably more. Then there exist ROM's which attempt to mimic the AOSP, Nexus-style experience. Plenty to choose from.
Click to expand...
Click to collapse
So basically My ROM territory is now limited to any 4.2.2 AOSP/AOKP Rom's ? Do all of them have on-screen navigation?
Like the Parandroid? No more Sammy Rom's obviously.
HellRazorGod said:
So basically My ROM territory is now limited to any 4.2.2 AOSP/AOKP Rom's ? Do all of them have on-screen navigation?
Like the Parandroid? No more Sammy Rom's obviously.
Click to expand...
Click to collapse
Hmm well I imagine you could find some lower than 4.2.2 with those controls if you wanted to, but no need to if you don't want. You can use ParanoidAndroid if you want, search my posts for a link for i9100, I posted it yesterday or the day before I think. It won't be the first link you find on Google thats for sure, version 3.6 is the latest. As far as 'limited to 4.2.2 AOSP/AOKP'.... Depends how you see it. I don't see it as a 'limitation'. Start here: http://forum.xda-developers.com/showthread.php?p=23231772. Go through AOKP and AOSP till you find something you like. Bear in mind that the AOKP contains waaay more than just plain AOKP, there's hybrid (combos of CM,AOKP,PA, AOSP usually) and all sorts in there.
Enable Navigation Bar in AOSP/AOKP roms etc for getting these functions back.
Alternatively if you want navigation bar in Sammy Roms you can still have them , look for soft key enabler in play store or else you can edit build.prop of your phone , there will be option of soft keys , change it from 0 to 1.
Use pimp my rom it have a option for on screen buttons (back menu and recents) so you can have any rom
Sent from my GT-I9100 using xda premium
S2 soft keys not working
Issue seems to be related to the usb charging receptacle. As long as a good charging cable is connected, the soft keys work. They work for a short time after unplugging and then stop working again.
HellRazorGod said:
Greetings my fellow XDA experts,
I have a Galaxy S2 (i9100) International version on the NeatROM 4.8 ( XXLSW). What has happened is that my Softkeys are dead and unresponsive.
There is no illumination and response from them. So I have a phone without the menu and back buttons, which implies that I have a f**ked up iPhone like phone with just one Home button to function with.
I took the phone to the service center and they said it's a single piece with the display so the entire display would need to be replaced which is unreasonable and needless since the display works absolutely perfect.
So I was thinking of a remedy in terms of the ROM I use with the phone. Is there any custom ROM available for the S2 which would enable me to use a part of the display as the MENU and BACK buttons itself ? Like the Nexus 4 has ? I don't mind losing out on screen space to enable me to get those buttons back.
Please do suggest me any such ROM's or methods through which I can use the phone without having to change a fully functional touchscreen display. Spending so much just to get the Soft key functionality back is plain ridiculous and a pure manufacturing drawback from Samsung. Yuck
Anyways, please do help with any pointers.
Thanks and Cheers !
Click to expand...
Click to collapse
So I was searching for the greater part of the last month, how to fix the home button lag issues.
And while disabling the double tap and long press questionably helps the situation, it doesn't actually fix the root cause: Oneplus' shoddy coding.
The issue is the Oneplus launcher. Simple fix is to download Google's Google now launcher from the app store. You could also use another ROM, but then you lose the fingerprint reader/laser focusing.
Bonus for you, if you have Xposed installed is that with Xposed GEL you can modify many of the launchers settings to your liking ... As long as Google doesn't break the GEL developers' app.
Hope this helps some of you. I'm now very happy with how this Oneplus two runs. And although we shouldn't have to do this out of the box, it's not too hard if you put in the effort and patience (plus you'll learn a thing or two about your phone).
Here's my configuration: Oxygen OS 2.1.1, Boeffla beta5 hotplug 2-4 & 0-4, Google now launcher, Xposed with Gravitybox.
I have been on Nova launcher from day one, and not a single hint of lag on the home button.
I loved to get rid of the this bug, but I really like oxygens shelf. In fact, it's the only thing that isn't crappy about their rom. Any chance to get this oder something similar with another launcher?
I have tried nova and action launcher sometimes my home button just stops working for sometime even the fingerprint scanner stops working.. I had to reflash 2.1 zip! And finally it my home button was back and then yesterday suddenly my home button again stopped working and I was pretty much frustrated abt this issue so I just removed the screen protector and it worked and even my fingerprint scanner suddenly became more awesome as it was just 80-85 % before.. now it's 99%.. I don't wanna return my phone as I heard it is some problem with the one plus fingerprint drivers.. And even few of 'em who got their phones on October had the same problem returned for replacement but they got the model manufactured from August.. So i think it's really not hardware it's a software issue!
Sent from my ONE A2003 using Tapatalk
TerminX said:
I loved to get rid of the this bug, but I really like oxygens shelf. In fact, it's the only thing that isn't crappy about their rom. Any chance to get this oder something similar with another launcher?
Click to expand...
Click to collapse
Google launcher is very similar to oxygen. You may not even be able to tell the difference ... And shelf is just recent apps (which GNL has in the app drawer) and recent callers list ... Which is in the recent callers list ...
you can fix lag in every buttom only if you disable function for double touch and large touch
Google Launcher jsut updated this morning. Give it a try. Also disable the double-tap function on home button.
Also using the screen bar buttons solve the problem. Releasing a phone with this kind of problems is a scam.
Enviado desde mi ONE A2003 mediante Tapatalk
jixbo said:
Releasing a phone with this kind of problems is a scam.
Click to expand...
Click to collapse
what?
fwiw, i don't seem to have any "lag" when the long press and double press is disabled.
But of course there is a lag when they are enabled. the phone HAS to have some way of realizing that you're not going to press it a 2nd time, or that you're not going to hold it down. how else is it supposed to do that? go to the home screen IMMEDIATELY and therefore not giving you enough time to press the button a 2nd time ?
lol use your brains people
oh and before anyone says.... i've used many roms on many phones which utilise the "double tap" and "hold home button" for different functions. every one of them has had a slight lag before it goes to the home screen. i dare say that you're remembering thing with rose tinted glasses if you're adamant that this phone is worse than those at this.
thefunkygibbon said:
what?
fwiw, i don't seem to have any "lag" when the long press and double press is disabled.
But of course there is a lag when they are enabled. the phone HAS to have some way of realizing that you're not going to press it a 2nd time, or that you're not going to hold it down. how else is it supposed to do that? go to the home screen IMMEDIATELY and therefore not giving you enough time to press the button a 2nd time ?
lol use your brains people
oh and before anyone says.... i've used many roms on many phones which utilise the "double tap" and "hold home button" for different functions. every one of them has had a slight lag before it goes to the home screen. i dare say that you're remembering thing with rose tinted glasses if you're adamant that this phone is worse than those at this.
Click to expand...
Click to collapse
With double tap disabled it also has lag with Oxygen default launcher. If you design something with lag by default, it is a really bad design. Try any nexus device (even nexus 4 is faster) or the OPT with cyanogenmod and you will see what speed is.
what? i don't think you understand what i wrote.
Nova launcher is the solution, still my best purchase from play store...
Hi Guys,
I have the same problem. I bought my OP2 during open sale, and i received a phone from the 06/08/15 batch. I have also a home button which is not very "responsive", but i think it's a hardware problem due with th metal frame. When I use a case, i don't have this pb and the home button is very responsive ( as it should be).
DO you guys experience the same?
I'm using Catapult Launcher. It's a fork of Trebuchet Launcher from Cyanogenmod. Works pretty good ... no laggs.
Gesendet von meinem ONE A2003 mit Tapatalk
Fellouss said:
Hi Guys,
I have the same problem. I bought my OP2 during open sale, and i received a phone from the 06/08/15 batch. I have also a home button which is not very "responsive", but i think it's a hardware problem due with th metal frame. When I use a case, i don't have this pb and the home button is very responsive ( as it should be).
DO you guys experience the same?
Click to expand...
Click to collapse
Yes. That's why I use the silicone case from oneplus. No problem whatsoever.
Sent from my ONE A2003 using Tapatalk
(Pretty much a crosspost from /r/Xiaomi cause I got no answer there):
Per the title: Once I had finally gotten past that Error 86006 stuff with bootloader unlocking and such, I immediately went to flash some custom ROMs on my Vince (since that was honestly what I had bought it for). One of the things I enjoy about those custom ROMs is that they often have the "Hold volume key to change tracks" function while the screen is off. Unfortunately, with any ROM I've tried so far (AOSPEX Official [7.1.1], LOS 15.1Unofficial [8.1.0, Non-Treble], RR 6.0.0 Unofficial [8.1.0 Non-Treble]), I've had an issue of my headset's buttons not functioning properly.
(Using CTIA/Android-compatible headsets [that also worked fine on my Kenzo]), whenever I press the top button, it acts identical to a middle button press, something I confirmed through the use of a KeyTest app I found on GitHub, showing a scancode 226 [HEADSETHOOK] for both top and middle buttons, while the bottom button was reporting as scancode 257 [BUTTON_2]. Not gonna lie; I don't really know the implications of that besides the fact that my top/middle buttons are essentially clones.
What this results in is: my top (and middle) button does the standard pause/play/skip track thing while my bottom button does weird stuff - sometimes acting like a "Tab" key would on Windows, selecting various boxes and then clicking on them. (Still not sure what it's doing.) This has been the same across 4 different headsets and it's becoming a bit irritating. I found some people with the same(?) issue with the Mi 2 and Mi Max 2, but the Mi 2's solution included some kernel tweaking for headset button electrical resistance (and I compared the values between the vince kernel dump and the ROM kernels and they seemed to be the same, so I dunno) while the Mi Max 2's solution involved some editing of the Generic.kl file in /system/usr/keylayout but that didn't work for me either. Has anyone else come across this issue/found a fix?
tl;dr: headset buttons aren't doing what they're supposed to in every single non-MIUI ROM I've flashed - some 7.1.x/8.1.0. Does anyone have a fix/the same issue?
I has same problem with 3 different headset. Non of them were working and no solution.
Same here. Any workarounds?