Develop Bugs

[Q] Which version should i use? (Not asking which rom is better)

Hello guys! I need your help and advise.
I need to use my kaiser to work. That's uhh.. receiving calls, making calls, sms, WiFi @ night to sync new contacts to my Google account... you know, small tasks.
I'm using as of yet CM7 with 2.3.32 (#63 IIRC) Data on SD Partition. Now.. although stable (no reboots, no crashes... seems OK) Its painfully slow.
If someone calls me, i have to wait about 7 ringtones before i know who's calling me. So.. i need your advise! Should i use a Donut ? perhaps a 2.6.25 ?
Please be honest, state your opinion and its basis
UPDATE 20110304:
I'm using as of yet:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
Battery rocks (i'm using a 2.8Ah).
Calls work pefectly.
SMS's work perfectly
Some apps apear to have a .... strange issue. They simply... don't open. But thats temporary. And a reboot fixes.
WiFi works (using latest from liquid with module update).
Quite happy
UPDATE 20110306:
Still no issues. One thing is granted, when i turn the WiFi on and let it sync... bogs down considerably. OC via atools to 490.
Will try the other option now, incubus26c's versions.
UPDATE 20110309:
Using incubus26c's with kernel .25 downloaded and edited through atools.
Been sufering from random phone problems. Simply shutdown. Cannot enable AirPlane mode. Have to reboot.
BTW, anyone has any other sugestions about roms ??
UPDATE 20110310:
Noted that my hardware keyb is sometimes eating letters... notably.. space.
Will check settings to see if disabling something helps.

Try using builds like those by incubus26c's or VaniljEclair. I've had both and enjoyed them greatly, going back to WM for the only reasons of better camera (autofocus never worked on droid for Kaiser) and ad-hoc WiFi support.
And... a few tips.
1. Use phone prioritizer (probably in VanilJEclair). This cuts delay between calling and receiving a call by two times.
2. Odexed firmware is faster, than deodexed. Yeah, no themes anymore, but you want a working device, not a box for bells and whistles, aintcha?
3. 2.6.25 is still up to date. Sometimes you'll need a patch to make wifi work, but that is a reasonable price for better speed.
What about donut? No, it is not faster then any 2.x droids.

StripezZ said:
Try using builds like those by incubus26c's or VaniljEclair. I've had both and enjoyed them greatly, going back to WM for the only reasons of better camera (autofocus never worked on droid for Kaiser) and ad-hoc WiFi support.
And... a few tips.
1. Use phone prioritizer (probably in VanilJEclair). This cuts delay between calling and receiving a call by two times.
2. Odexed firmware is faster, than deodexed. Yeah, no themes anymore, but you want a working device, not a box for bells and whistles, aintcha?
3. 2.6.25 is still up to date. Sometimes you'll need a patch to make wifi work, but that is a reasonable price for better speed.
What about donut? No, it is not faster then any 2.x droids.
Click to expand...
Click to collapse
Clear enough.
Will report back with more info
Thank you

1st Post updated.

And again.

Still no issues. One thing is granted, when i turn the WiFi on and let it sync... bogs down considerably. OC via atools to 490.
1. get RogueTools from Market to overclock the device without atools
2. a question from my side: are Gingerbones worth it?

I actually used and tweaked a Gingerbones. Was quite good, not as fast of course, but then again, more eye candy.
I'm not getting any instability, just plain ... slow during sync. But this as been a standard with any version i've tested.

wifi sync lagging seems to be quite common for all low-end droids, both native and cooked. As long as it happens mostly with encrypted networks, i would suppose the reason is some sort of cryptographic calculations MSM72xx delegates to CPU.
Though, since all unsecured networks I encountered were very slow (256k or so), there's a chance the lag nests in higher bandwidth, causing data to be downloaded a bit too fast to be processed - sometimes HSDPA connection makes the gadget lag, too.

daedric said:
UPDATE 20110310:
Noted that my hardware keyb is sometimes eating letters... notably.. space.
Will check settings to see if disabling something helps.
Click to expand...
Click to collapse
There is strange polling behavior with hardware keyboard on 2.6.25
Though I love stability in 2.6.25 kernel, the Eating of Space button is quiet frustrating when I am texting my boss :| (which I often do) and I press Enter to send right away (just as I am chatting).

StripezZ said:
wifi sync lagging seems to be quite common for all low-end droids, both native and cooked. As long as it happens mostly with encrypted networks, i would suppose the reason is some sort of cryptographic calculations MSM72xx delegates to CPU.
Though, since all unsecured networks I encountered were very slow (256k or so), there's a chance the lag nests in higher bandwidth, causing data to be downloaded a bit too fast to be processed - sometimes HSDPA connection makes the gadget lag, too.
Click to expand...
Click to collapse
So... if the massive slow(ness?? is this a word??) is coming for a bogged CPU on SSL encode/decode, we could... say... use OsMonitor to check?
Which process should be giving lots of CPU usage ?? Android System ?

dark_prince said:
There is strange polling behavior with hardware keyboard on 2.6.25
Though I love stability in 2.6.25 kernel, the Eating of Space button is quiet frustrating when I am texting my boss :| (which I often do) and I press Enter to send right away (just as I am chatting).
Click to expand...
Click to collapse
So... perhaps moving to 2.6.32 should provide me with it a better keyboard polling, at a stability price ??
P.S.
Anyone else would like to suggest another rom ?? BTW... i'm going to try and strip a gingerbones (by Aceyome if i remember his nick right) to gain extra stability.

I think yes. Though I have used .32 kernel for so less time than .25 so as I need the Mass storage functionality, which works perfect with dual mount on .25 kernel. Try Fat Free Froyo by thoughtlesskyle, if you really want a vanilla build

dark_prince said:
I think yes. Though I have used .32 kernel for so less time than .25 so as I need the Mass storage functionality, which works perfect with dual mount on .25 kernel. Try Fat Free Froyo by thoughtlesskyle, if you really want a vanilla build
Click to expand...
Click to collapse
Hey dark_prince, OFF TOPIC question:
How is the Froyo 2.2 x86 ?

daedric said:
Hey dark_prince, OFF TOPIC question:
How is the Froyo 2.2 x86 ?
Click to expand...
Click to collapse
Still not to be used as Primary OS. Alot of things don't work and force close on my D420. Though x86 build works pitch perfect with an EEEPC. It's blazing fast and stripped down to just 80MB and has Hardware OpenGL ES support for intel 915,945,965 chipsets. 1280x800 isnt supported fully as of yet (You can run HDPI one). Market doesnt work, but a proprietary App downloader is provided. Also, keyboard works perfect and mouse emulation is nice. Ethernet + Wifi support depends if kernel supports.

Why doesn't the market work??
(market! y u no work?)

daedric said:
Why doesn't the market work??
(market! y u no work?)
Click to expand...
Click to collapse
It crashes randomly with the build, thats why it was removed. But there is another handy app installer which comes with every x86 build

[Q] optical trackball problem - any way to disable the sensor?

After some water exposal, bottom hardware buttons (along with optical trackball) refused to work.
I have fixed them with some precise inside cleaning, but the optical function (not the button himself) continues malfunctioning, which is not a big deal for me, but..
The exact problem: i spotted in dark environment, that the sensor inside continuously glimmers in all modes - scren-off, scren-on (without puting finger over him), etc.. In return, my battery drains extra aprox. 10-12 mA!
I have observed, that in healthy device, sessor glimms only when interacting with him..
Is there a chance to disable this sensor to avoid this? I hope in software manner

I don't think there is anything out there that will disable the optical pad. You could give HTC a call or your carrier and see what they say.

There is this thread on the forums about turning off the backlights.
Should work for trackball as well? Probably. Something about LED Hack on the first or second page. Seems to be something on the 3rd page as well.
Go have a read over here (I just skimmed. its 2am lol) http://forum.xda-developers.com/showthread.php?t=704977

@formformer
If you tell me your kernel version I will try to build a kernel without trackpad support!?

@Meaple 's post was sadly adequate and rips best hope in me ;( ..
@eden2812 I have using 2 led hacks from previous attempts to minimize energy consumption & eye comfort, and they shurely don't do the "trackpad sensor shutting" job..
@AndroidJaspie
it's so damn cool to offer this kind of experience. salute!
i have likely using latest Ginger Villain's compilation, but any recent rom-kernel set, with weak appetite fits my best.
i will be very patient to hear from you..
my current setup is:

OK I built a new kernel from the cyanogenmod sources now without trackball support. I tested it with GingerVillain 1.4 and it worked.
please make a backup and then give the update.zip a try.
Tell me if the new kernel solved your problem or not.
Jasper

Yes Jasper, obviously the sensor is shutted (no glimmering observes) and the xtra drain is all gone now!! I'm so pleased.
But i have found, that the bottom buttons (including the button under the optical trackpad) not waking the phone any more. Is this issue related?
And another, not so important question: Would be this kernel compliant with other Gingerbread releases? or.. could you give me some hint, if is possible to transform your "surgery" into a some kind of a patch, that will give me opportunity to enjoy any feature kernel/roms?
Again, BIG 10x for your respond in this custom problem so far! You make my life happier
karel

No problem i like it to work with things like that. So it's a good chance to improve my knowledge about linux and help other people at the same time.
Are you talking about the all buttons or only about the button around the optical sensor?
If you are talking about the one around the sensor then it's normal that it won't wake up the phone any more. But the others(home, menu, back and search) should work like before.
This kernel works only with cyanogenmod and GingerVillain. On other rom's like Oxygen it doesn't work. But you i can compile you the kernel you want.
At the moment it's only possible to disable the trackball only by editing the kernel configuration. But i will try to get it working without changing the kernel so that you can use every kernel you want.
Jasper

i told so, about the relation of shutted sensor and not working buton.., but yes, others buttons also not working in lockscreen-off mode, where they should or at least worked before. (volume butts still works for wakening..)
ps. a have barely no linux skills, but its interesting for me either!
and if editing & compiling is not so high level task, im going to try first steps right now!
Any way, disabling track sensor without editing kernel settings sounds like a dream..
k

hi, my fried
could you tell me, where in the config I can find the exact setting and how to change it?

hi
if you got the kernel source you can make menuconfig to configure the new kernel. To disable the trackball go to "Device Drivers" --> "Input device support" --> "Opticaljoystick". To disable the joystick press "n" to enable it press "y"
Don't know how to comile your own kernel?
here is a useful links that helped me, too:
-[HOW-TO] Build your own kernel package from source

huh.. 10x 4 the guides, they light me enough to get started week ago, but i get stuck just in the beginning (problems with MBR or something..). and at this moment i have absolute lack of time to deal with this interesting stuff. However.. can i have one more last ask from you: to compile for me an updated kernel.. (they says he has the ability to record 2way call conversations..)
Using the Ginger Villain rom, suppose with this richardtrip kernel. Guess CM will worx too..
Thanks anyway!

ok
a bit late but here it is
a new kernel version 2.6.37.2 from the richardtrip-sources.
kernel features:
-disabled trackball
I don't know anything about "Two-way call recording kernel support" but i will try to find out as much as posible to configure a kernel with it.
jasper

Hi AndroidJaspie, i've the same problem with the optical trackball of my desire. I use the miui rom with the kernel 2.6.37.6-cyanogenmod-g8913be8. Can i use the kernel in your last post? thx bye

Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] CIFS/SMB kernel recommendations for Synergy (Or other Sense ROM)

Wow, XDA found my original thread back in the day (it does a search when you create a title):
http://forum.xda-developers.com/showthread.php?t=984254
I've come a little ways since that thread, but I'm still in "clear as mud" territory.
I am running Synergy (just flashed a few days ago):
http://forum.xda-developers.com/showthread.php?t=1144447&page=1544
and would like to add CIFS support. This is a networking component, not a scheduling component (I'm getting pointed to CFS/BFS kernels is why I point that out).
I have downloaded CIFS manager and it seems that CIFS is not built into the Synergy kernel (I get an error: Mounting the share has failed with an error. Mount: no such device) so I would like to add it. Problem is, I'm having a hard time finding a sense kernel that adds CIFS.
I found this guide:
http://forum.xda-developers.com/showthread.php?t=894880
and this one
http://forum.savaged-zen.com/showthread.php?6-HTC-Evo-(Supersonic)-Megathread&daysprune=-1
while researching kernels and how to load them. I think I have the process down, I just need to find one.
*edit* I found this one: http://forum.xda-developers.com/showthread.php?t=1192796 Golden Monkey. He says it's still in development though. I'd prefer a release version if I could get one.
In case I wound up looking at the wrong ROM/kernel, I would like recommendation(s) for ROM/kernels with the following criteria:
Must-have's
sense 2.x or 3.x based
gingerbread based
working 4g (I do have 4g in my area)
working HDMI (I would like to start using webtop)
Really want's:
CIFS kernal (a must have, but if I can flash a kernel onto a ROM I'm good)
Would really like:
bluetooth profiles like keyboard, mouse
USB host support
Not interested in:
overclocking/underclocking
adjusting voltage
changing scheduling (CFS/BFS)
god mode (not at the moment anyways, maybe later)

Well I tried Synergy-Kingdom 7/23 and it was kinda slow, so I dropped back to Synergy and flashed the Golden Monkey kernel So far, it seems I have everything I want, although I haven't tested 4G and HDMI yet today.

Attempting development for Gingerbread. (Long post/discussion)

Hello everyone...I'm planning on trying to develop a gingerbread kernel for AOSP because we don't really have support anymore and everyone has moved onto developing for ICS (not that this is a bad thing). I figure in my spare time I might as well try to learn and develop for our phone. Let me start by saying I was never really into phones/smartphones/rooting, or software development, but I've always been fascinated by Linux in general. I've played around using a number of Linux distros, but I've never really done anything intensive with them (modified their kernels, etc.) but I am vaguely familiar with terminal usage.
Anyways that was just my introduction. I've been running an ICS kernel on my AOSP GB system (specs/stuff in my signature) and while most advised against it, I find it to run pretty well. I'm not sure why it seems to run so well on my phone, but it's basically solved most of my problems (or at least it appears to have done that), but I know the kernel isn't "optimized" for my phone. Some major things people have said are that the ramdisking operations/system is totally different when comparing ICS and GB. This kernel that I'm using is running pretty well, even knowing this fact. What I was wondering is if I could basically get the ICS kernel, then "merge it" with a GB kernel's parameters that pertain to the ramdisk/other major options of GB. That would probably make it better. Also, people stated that multitouch issues for the DINC2 occured on Aeroevan's 0.8 kernel, but not on the 0.7 kernel. This was the changelog stated by aeroevan:
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.
Click to expand...
Click to collapse
So maybe this "small touchscreen driver update" is the thing that caused it, but I'm assuming many other kernels applied this update too? Maybe there is a way to roll back to whatever was in 0.7 in this sense to get rid of the multitouch bug that plagues some people.
I have a pretty powerful laptop, so development shouldn't be too bad. I plan on running Ubuntu 11.10 (or whatever people find suitable these days) in a Virtual Machine and I plan on compiling stuff from there. I am not claiming I know everything or that these things are correct....I am simply just throwing out some brainstorming to get some ideas out there. I know GB is "old", but I (and some others as well) enjoy it's stability and that it generally functions perfectly. Maybe this thread will get a look from popular devs, or maybe it'll get a look from people who just know this stuff. Thanks for reading, and sorry for the length of the post.

Looking forward to your progress on this.
Sent from my ADR6350 using xda premium

It would be nice to have another kernal for AOSP other than aero.

Your help in developing AOSP kernels would be fantastic.
Thanks given. Because I am hard of hearing I cannot use any of the kernels (even Evan's) and have to stick to Sense

[Q] Why is ROM-cooking so hard?

Hi!
I have great respect for the people that give us our great ROMs, and i KNOW that that is hard - but my question is: why exactly is it that hard?
This is just a question out of curiosity, because I would really like to understand the unerlying problems that cause all the other issues.
I was under the impression that the Android stack runs on top of the Linux kernel.
Usually, the Linux kernel is the Hardware Abstraction Layer, and apps and ROM, in theory, should be kind of hardware agnostic?
e.g. the Bluetooth Issue on our Captivate Glides: I would guess that Android communicates, through some API, with the kernel's BT stack/driver. There must be some (open or closed source) driver available (worst case: some .so module ripped out of an official ROM, maybe?). So why does the headset profile not work? Did the APIs change? Are custom ROMs forced to use another version of the driver?
It also happens to this 50$ chinese tablet i have here: some ROM screw up the touchscreen, some break audio, and so forth. Why can't there be some way of installing a generic ROM, and then side-loading the OEM's drivers?
Thank you again to all ROM developers! This is NO WAY a complaint. Just pure curiosity!

I may be out of my league when trying to describe this, but the processor in our phones is somewhat different to the processor in the bulk of other phones. This is where majority of the issues came from in porting ICS to the glide before ATT released it. Even after the first official ICS update, the modders here were the ones who fixed the keyboard lights... I changed up to JB because the GPS wasn't locking quick enough and PACROM had all the quick toggles and the speed/gps lock I needed.
Sure the kernel is the underlying part that pulls it all together, even still there is all the drivers that need to work with it. If there isn't a bluetooth/wifi/HW Video driver for the version of the kernel, then it gets really tricky and now its coding for a piece of software to speak with the hardware ..... We have things that partially work, but not fully ...as with everything computers, in theory things that "should" work, don't always... I'm an IT tech.. I run into weird **** all the time that "should" work ... takes time, but with persistence and the right skillset, majority of the time a resolution can always be found.