yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] RXDriv3r:
Ok first and foremost...I have tried searching :D

I have been a lurker most of the time here on xda seeing as if I just search and read I'll get most of my answers, but not this time.

Ok some background info first:

TMOUS US HD2 1024Leo

Radio: I'm not 100% sure but I did a task29 that supposedly flashed 2.15.50.14

HSPL: 2.08

MAGLDR 1.13

I bought this phone about a year ago, flashed tytung's Nexus HD2 Gingerbread rom which worked flawlessly for about 10 months or so. One day the phone froze up, pulled battery then inserted and the rom reset to the point where it was like new. Around that time tytung's ICS AOSP thread came alive and I followed it closely watching the updates and what not.

I never installed it until Beta 10. Followed his instructions, set up the partition to 200MBs with a cache of 45MB...45MB for cache because I suspect I may have some bad NAND blocks. Anyways install went flawlessly, everything that was supposed to work, worked...ect ect

Used it for about 24hrs then all of a sudden it froze, when I rebooted I started getting all these random apps crashing(gapps[google apps?], Email, Google Login Services ect), needless to say I task29'd the HD2 and reinstalled everything, worked fine for a day then everything started crashing again.

So after all that info I'm just wondering if someone is experiencing the same problems and/or can maybe lead me in the right direction to figure out this problem.

I know its only a beta but I havent read many posts containing my problems. So Im just left wondering if my NAND is going bad completely and I need a new phone or if theres just something I'm doing wrong.
[HD2 Android Q&A, Help & Troubleshooting and Genera] matoflash:
Before i begin - I have no experience with that Rom, these are just common general ideas.

1) as the rom starts well and then only after a day it breaks, maybe it is because of something (update) getting installed on your device. Have you tried fixing permissions after you encounter the problem?

Or try figuring out which update of which app does it.

2)It also might be the problem of the nand bad blocks, if you suspect it, but if thats the case, there is not really a lot you can do...
[HD2 Android Q&A, Help & Troubleshooting and Genera] kylew1212:
No offense, but that's the reason its beta. It doesn't have all the bugs worked out yet.

If you're looking for a daily driver, you should try something more stable.
[HD2 Android Q&A, Help & Troubleshooting and Genera] onlinegames:
Hi,

Not sure if you still have this problem..

Have you tried re-installing the ROM again or a different ROM to confirm if the issue is with your phone (hardware) or with the ROM (beta version)?
[HTC Wildfire S] ONeill123:
Hi all,

i have only one question:

Is it possible to port the 4EXT Recovery Touch to our great Wildfire S?

Thanks for answers!
[HTC Wildfire S] insink71:
anything is possible

Sure. Though it would take some serious work AND I don't believe any of the devices they now support are nand like ours :( So we'd have to have a good bit of money, go up and court Madmax and pick his brain, then write it... then send it back to Madmax for approval/inclusion of his app. It would be nice but the amount of work... staggering [for someone not on the 4ext team].

I did look into it and even got his permission to try... but definitely too big a project for me to do solo; so, it's on my "I wish" stack ;)

Rob
[HTC Wildfire S] ghiki:
I taked with madmaxx, it's developer and it says that's hard because WFS's xresolution (I suppossed because Desire [originally 4ext recovery device] has 800x480px resolution )
[HTC Wildfire S] eoghan2t7:
what if the recovery was set to landscape?
[HTC Wildfire S] insink71:
Yes you would have to resize all images. That would take some time but easily doable. I'll work on the images when I get frustrated by Europort. The recovery itself... We need to work together on; I came from g2 and incredible 2. His recovery partitions then checks partition alignment something I've not seen elsewhere; then last time I turned on the g2 visual too [lot more images]. It should be ported if possible but would take time if I had to turtle it alone.

Rob

Honestly, I'd try non-visual just for the partitioning tools as a primer.
[HTC Wildfire S] insink71:
Forget last statement the images will have to be made and submitted for approval to Madmaxx.. I haven't seen what images are in his apk. So you got images for apk [which you submit for approval], images for recovery, rewrite the recovery for nand; I can't sign up for overwhelment ;)
[HTC Wildfire S] insink71:
It is akin to attempting a miui port on a smaller, more detailed scale. ;)
[Galaxy S II Q&A, Help & Troubleshooting] GuestD1093:
Hi guys,

I would like to know the reason why the people who call me hear me very bad if the Noise reduction is active. I have read all the posts from here but I could not understand exactly if this is a hardware problem or a software problem. If 100% is a hardware problem I will sent my device to the service but if it is a software problem I will try to change the baseband ( now I'm on XXKI1)

10X for your answers
[Galaxy S II Q&A, Help & Troubleshooting] sxi200:
On checkrom v4 there is a phone mod which has it set to off by default. Also, it is common knowledge that using a case causes an echo on the other end.

Sent from my GT-I9100
[Samsung Galaxy Nexus] beekay201:
W00t fugumod on the nexus!! :)

Will try it, thanks for dropping this here.
[Samsung Galaxy Nexus] zurchpet:
I'm totally happy :D
[Samsung Galaxy Nexus] Nitroz:
Finally! A kernel we can rely on :) Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
[Samsung Galaxy Nexus] renaud:
You probably mean SGS1.
[Samsung Galaxy Nexus] j.go:
I'm not entirely sure how accurate setcpu is at reading frequencies, but it seems to be stuck at 700mhz after a reboot. Moving the sliders a bit allows the cpu to use the entire range of 350-1200mhz as intended. I'm on AOKP milestone 2 if it matters and using r26.
[Samsung Galaxy Nexus] beekay201:
Haven't yet tried this, but maybe min frequency when booting is set to 700mhz?

when you open setcpu, is the min slider at 350mhz?

What governor are you using? Not sure it matters though, but it might so.
[Samsung Galaxy Nexus] renaud:
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies

Sent from a Nexus
[Samsung Galaxy Nexus] j.go:
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.

Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.

EDIT:

I don't seem to have an init.rd file anywhere. I did a search using root explorer.

Edit 2:

CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
[Samsung Galaxy Nexus] renaud:
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
[Samsung Galaxy Nexus] j.go:
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
[Samsung Galaxy Nexus] renaud:
Try the latest version, I removed all Francisco tweaks.
[Samsung Galaxy Nexus] j.go:
All right, I'll give it a spin tonight and post how it goes. Thanks!
[Samsung Galaxy Nexus] renaud:
I think I will be upgrading my phone to 4.0.3. This would mean I would not support 4.0.2 as I would not be able to test it properly. Are there users here who need the 4.0.2 version?
[Samsung Galaxy Nexus] zurchpet:
great

R37 für 4.0.3 runs flawless.

I use CM9 kang by fitsnugly.
[Samsung Galaxy Nexus] zurchpet:
R40 also flawless on fitsnugglys CM9 kang :)
[Samsung Galaxy Nexus] renaud:
r41 is out, probably last release for today
[Samsung Galaxy Nexus] zurchpet:
I flashed the latest KANG from today and the 122211 gapps with R41.

Works like a charm so far :)
[Samsung Galaxy Nexus] beekay201:
aosp kang built today, flashed R43 just now. booted fine first try, wifi/bluetooth are fine, data call as well, rebooted, set scheduler/gov to deadline/ondemand, min/max freq to 1.2ghz, score on antutu maxing out around 5200, 5300. with my modified stock, i hit 6200+ in those conditions.

switch back to cfq/interactive, sd write speed goes up a bit to 10.4mb/s (deadline was just under 9.4mb/s), cpu integer 1304, float 1099, pushes score up a bit but still not reaching 5400 (this is with all tests selected, 2d/3d, database..). tweaked lowmemorykiller, antutu score jumps to 5600+.

but benchmarks mean almost nothing, i know. overall it's pretty smooth, fast on bootup, ocasional "lag" here and there (but that may be Mr. Android's fault).

will report more as the kernel settles in.

thanks nikademus. :D

edit: just re-installed gta. it seems i have no in-game sounds at all? it's fine until it gets to the main menu though. anybody else seeing this? happening on stock kernel too, wth..

edit2: jumping on r44.
[Samsung Galaxy Nexus] zurchpet:
flashed R44 on the latest fitsnugly kang. all is well. as expected, as only unused modules have been removed ;)
[Samsung Galaxy Nexus] pedmond:
124 seems great. Not that I expected anything less than that from Nikademus. Thank you again :)
[Samsung Galaxy Nexus] manager77:
r124 works great...thanks!
[Samsung Galaxy Nexus] renaud:
How is the battery with r124? Does it feel faster? Don't hesitate to report, but please don't report with benchmarks, most are completely flawed, this is only subjective reporting I am asking. The most important is not how fast the phone is, but how the phone feels.
[Samsung Galaxy Nexus] manager77:
battery is good to me(drains 1% :2-3 hours in standby and 4-5 min. with screen on)......all seems to work ok, no problems so far...it is smooth and stable..
[Samsung Galaxy Nexus] Gregus59:
Battery drain is ok for me with 124, but I have a connection drop, I don't know why...
[Samsung Galaxy Nexus] renaud:
You are playing too much with basebands :D
[Samsung Galaxy Nexus] Gregus59:
... Lol... :p...
[Samsung Galaxy Nexus] slyydrr:
Phone feels good to me so far on r124! I'll check back in after another full day's use.
[Samsung Galaxy Nexus] kizaros2g:
finally able to download your kernel! so far so good, going to test more on it. fyi, im using r124 ^^
[Samsung Galaxy Nexus] fiftyclick:
Hard to compare the relative performance, as this is the first time I am flashing one of these kernels, but after one day everything works great so far. Respectable battery life, no noticeable lag, and benchmarks fairly high. Gonna stick with this one for a while. Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] xdafann:
How is the GPS working for you guys?
[Samsung Galaxy Nexus] renaud:
Just tried right now, got 7 sats in less than 10s

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chadouming:
Hehe, nice to see you here man, i remember your SGS I kernel and i cant wait to see this one performing.
[Samsung Galaxy Nexus] rashidi_zin:
Locked my location really fast. Within 10 - 15 seconds.
[Samsung Galaxy Nexus] slyydrr:
I hate to say it, but after 36 hours and 2 charges on r124, the battery life for me is worse than with r115 (I believe that's the release I was using prior). Not significantly worse, but definitely noticeable. My usage habits didn't change between the previous release I had, but I usually only charge once after about 36 hours with about 10-15% left. The past 36 hours I had to charge in the middle with about 30% left and am now again at 32% after another day's use.

I know you're concerned more w/ stability and security, but you did ask about battery so I'm telling my results :)
[Samsung Galaxy Nexus] renaud:
Thank you, try setting the scheduler back to cfq to see if it helps.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slyydrr:
You bet sir, just trying to help. If you don't mind me asking, where might I set the scheduler?

EDIT: A little digging beyond what I tried at first got me to think something similar to the following might work, but being that I'm a novice in this area, I don't want to naively do anything stupid... echo cfq > /sys/block/mmcblk0/queue/scheduler by chance? I'm not sure which disk in the /sys/block it is, but mmcblk0 looks familiar.
[Samsung Galaxy Nexus] renaud:
Yes, that will do it, or you can use an app to do it, like "pimp my cpu"
[Samsung Galaxy Nexus] renaud:
r133 contains some wifi fixes

r134 has BFQ removed, it did not give any noticeable performance gain.
[Samsung Galaxy Nexus] Gregus59:
Official release of CM9 nightly build + r134 work like a charm... ;-)
[Samsung Galaxy Nexus] !crazy:
What do you mean by factory image? Factory image is Google's stock ROM. Try Jame Bond 007 kernel. For me it is the most stable kernel I was using since 4.2.
[Samsung Galaxy Nexus] sk8oldschool74:
I'm not on factory image at the time it is backed up I'm currently on fnv 4.1.1 v008.... best ROM ever...:D:D:D

---------- Post added at 06:07 PM ---------- Previous post was at 05:55 PM ----------

I also noticed w/ this kernel I get almost 400 GB of ram as to were we/ fugumod I get under 100...:(:(:(
[Samsung Galaxy Nexus] tibere86:
v1035 is smooth as all hell. Smoother than Trinity or Franco. Can't believe it's only running at 350mhz/1200mhz...feels overclocked :)

But for me, idle battery drain has been subpar compared to the aforementioned kernels. Hopefully it will get ironed out with future releases.

BTW running 2012-12-08 Rasbeanjelly 4.2
[Samsung Galaxy Nexus] renaud:
Which game? Don't forget that this kernel is using enhanced security features, so if one app doesn't work, I would examine it further.
[Samsung Galaxy Nexus] !crazy:
With fugumod you probably get reported RAM which is completely free, and app cannot determine buffered and cached memory. But I am just guessing.
[Samsung Galaxy Nexus] !crazy:
As I have already mentioned I am running Jame Bond kernel for couple of days and it runs rock stable. But actually the thing is I have disabled 'Location access' all that time.

With FuguMod I was usually having it enabled. Now I have flashed Fugu, and will try running it with disabled location. Although the reboots are not the only problem I had with FuguMod, the screen used to freeze sometimes, and I had to pull the battery, but who knows, maybe that problems is caused by the same bug. Anyway I am trying it now.
[Samsung Galaxy Nexus] renaud:
Depends on the app, most apps don't have permissions to see what other Apps are doing, which means they won't be able to report any usage. That's a security feature and I will not disable it.
[Samsung Galaxy Nexus] !crazy:
I am not against that feature. I am just trying to explain him why he sees only 100 MB free memory with fugumod, but other kernels always report more memory as free.

Even stock system app cannot determine how much memory an app is using.

---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------

Did you actually find an app which can report how much memory is being used per app?
[Samsung Galaxy Nexus] !crazy:
Didn't last long. I have just got a new freeze with FuguMod, with location access disabled. Had to pull the battery out. MPU wasn't' hot but these freezes usually happen when I am using a touchscreen a lot. It has happened when I tried to open HD widgets settings, but that's probably coincidence.
[Samsung Galaxy Nexus] sk8oldschool74:
I've ran dr. Webb light and no security issues w/ it... do you have a recommendation... it is called outlaw...

You will see it in the bottom left corner...;):)
[Samsung Galaxy Nexus] renaud:
I have yet to see any reboot or freeze with 1035. I have location services enabled and latitude too.
[Samsung Galaxy Nexus] !crazy:
It probably depends on usage. From the picture you attached I can say you are not using it much as I use my phone (sometimes).
[Samsung Galaxy Nexus] sk8oldschool74:
I notice I actually loose ram on this kernel??? :confused::confused::confused:
[Samsung Galaxy Nexus] !crazy:
I don't thinks so. Other kernels repor buffers and cache as free memory, actually the apps do that, and with fugumod they report that same memory as occupied, I thinks that's the situation, but I am not 100% sure.
[Samsung Galaxy Nexus] sk8oldschool74:
This is what my ram looks like on current kernel... no apps removed or added...:(:(:( when running fugumod I get under 100mb of free ram...:confused::confused::confused: I am only posting to try and help....;):) Renaud try star kissed and see if it is just me.... no reboots or freezes... Just trying to help as I said before...;):)
[Samsung Galaxy Nexus] odin13:
That is no kernel problem...

I had the same thing today. Suddenly my phone became very sluggish. There was only 50mb free ram...reboot 'fixed' it.

I'm on PA 2.99b7 with AK 457 kernel.

Still i have no clue what was keeping all the memory in use...strange but definitely not a fugumod problem :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] sk8oldschool74:
I tried reboots and still under 100mb of ram... maybe my phone is just ready to be updated to the n4...;):) Thanx odin13 for always being there looking out for me and taking the time to thank me... it means a lot my friend...;):)
[Samsung Galaxy Nexus] rashidi_zin:
Seems like the problem where my phone refuse to wake up still persist :(

Funny thing is there was no application running.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
There is now r1036 with linux 3.0.56
[Samsung Galaxy Nexus] odin13:
No problemo :D

I still haven't figured out what is causing this...currently i have > 100mb of free ram....aaargghh strange!

Somehow there is a memoryleak or something like that

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] renaud:
as a test, in r1040, I have completely disabled the watchdog to see if it solves the reboots some people have. If this translates to lockups, then maybe the watchdog was working correctly.
[Samsung Galaxy Nexus] odin13:
In my case it was the rom...PA2.99b7 somehow uses up all the memory.

Back on beta 6 i have some 300mb free ram :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] !crazy:
Thanks I'll try this. Back in days when I have used to compile kernels for Slackware and Gentoo I almost never included watchdog. Better lockup then reboot : ). Let's see now...
[Samsung Galaxy Nexus] !crazy:
Renaud,

I would have another feature request... Could you pls add fast charge if possible? I am using Google navigation sometimes, and without it battery discharges actually.

And again (I know I am boring) is there a way for you to not to leave GPU underclocked without increasing voltages. We could actually check what the SR is doing and how big isbtne difference if any. If SR calibrate to little higher values, I would like to try running 384 with same voltages as with under clocked GPU.
[Samsung Galaxy Nexus] !crazy:
I have just had another reboot. The phone was was charging with screen off.

Here if someone want to check last_kmsg
[Samsung Galaxy Nexus] nicholaschan24:
On 4.2 r1040. Only had 1 reboot in past 24 hours. Massive improvement! And the reboot was probably due to os. Thanks renaud!
[Samsung Galaxy Nexus] sk8oldschool74:
What is the purpose of deadline???
[Samsung Galaxy Nexus] renaud:
Deadline is an IO scheduler, like CFQ, some people prefer it over CFQ on flash devices.
[Samsung Galaxy Nexus] jbeez:
Im having lockups on 1040 and iirc more reboots on 39, but id rather it reboot than lock and miss a wakeup alarm or just not know its locked till i goto check my phone and pull it out of my pocket
[Samsung Galaxy Nexus] renaud:
r1041 has linux 3.0.57

r1043 has the watchdog enabled again
[Samsung Galaxy Nexus] !crazy:
There was a talk about screen lock and touch wake. I am not sure what was/is meant by screen lock here. What happens to me is that, usually after I end received call screen locks I have to type the password again (I cannot remember if that used to happen while I was using pattern.) to unlock it.

Not a nice bug. Typing a long password each time after the phone conversation (when I am not the one who calls.) is PITA.

What I wanted to say, this has nothing to do with this kernel, or even GN kernel. The same thing started happening with my galaxy note 2 after I encrypted it (I am not 100% sure if happened before encryption.). It happenes also with SG3.
[Samsung Galaxy Nexus] renaud:
You can put a short screen lock pass and a strong boot pass, look in the market for encpasschanger. Put a 5-6 digits screen lock, then use encpasschanger to change the boot pass.
[Samsung Galaxy Nexus] !crazy:
Thanks!
[Samsung Galaxy Nexus] renaud:
Also, if your phone is encrypted, don't forget to remove USB debugging or else it's trivial to steal data with adb.
[Samsung Galaxy Nexus] renaud:
r1047 some changes to interactive governor

r1048 added BFQ scheduler (take care, it may not boot each time, it seems BFQ hasn't been fully fixed yet)
[Samsung Galaxy Nexus] tibere86:
Thanks! Flashing r1048 now.

Edit: r1048 would not boot for me. Back to r1046
[Samsung Galaxy Nexus] renaud:
You can try booting 1048 multiple times, at some point it will boot. That's unfortunate, but BFQ is still not fixed at that point. Mine booted at first time though.
[Samsung Galaxy Nexus] !crazy:
Thanks Renaud, I knew that, I have read OP : ). I must say it is too bad you kernel doesn't work stable on my device. Jame Bond kernel is really rock stable. I must ask him which linux he is using. Maybe new sources are not so stable, and I see a lot of folks are complaining on instability in most topics of popular kernels, and it looks like there is a competition who will update first. Ezeekel always stayed on official stable kernel because of stabilitty.

---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------

Stupid me, why ask when I could simply check kernel version under 'About phone'. Like I thought it is 3.0.31.
[Samsung Galaxy Nexus] ak:
fugukernel

most of the time the kernel patch should not be even touch the features provided by android,,, and instability in my opinion can not refer to them.

I used for a long time fugukernel the relationship stability update has always been great.

It 'logical that the less you updates = less problems you may have = then it is better to use the stock kernel! :good:

Peace and Love.
[Samsung Galaxy Nexus] renaud:
r1049 disables BFQ by default

r1050 makes some changes to the wifi driver