Linux on the blue angel - some problems - MDA III, XDA III, PDA2k, 9090 General

Hi!
I installed Linux / GPE on my MDA 3 following this link
http://handhelds.org/moin/moin.cgi/BlueAngel
The installation worked well (thanks guys) but I have some I hope little problems.
I have a german qwertz keyboard and I can not use the it the right way.
Especially the fn + key stuff does not work. So I can not use characters like % & / * # - and so on. How can I set / configure the keyboard stuff? I guess I need a german keyboard layout.
The second problem is, that the sleep configuration does not save my settings it hangs. So sleep works and the device collapses after 6-7 hours because the battary is empty. This results in a time consuming reinstall of windows CE. Is there something I can du about this?
Thank you for any help.
Regards

Missing "deep sleep"
To me it looks as most modules dont treat the apm states at all. So beside the wake up IRQ`s and RAM , nothing needs to be awake.
Also the CPU might miss to really fall deep sleep on the Blueangel.
Those things need to be still added and coded.
Regards

Related

CPU overclock

does exists a software specially for overclocking my P3300 CPU? I tried xscalar, or something like that, but it takes my device only on 196 mhz, starting from 133mhz (or this 133 is over my 200 mhz by default?)
ady_uaic said:
does exists a software specially for overclocking my P3300 CPU? I tried xscalar, or something like that, but it takes my device only on 196 mhz, starting from 133mhz (or this 133 is over my 200 mhz by default?)
Click to expand...
Click to collapse
Download BatterStatus Extended V. 1.04 Beta nightly build here. Every owner of P3300 has this installed. For more info... search this thread.
i've downloaded, and installed it. but my drain battery is very very very faster, in 5 minutes, drained 9%.
so what can i do?
ady_uaic said:
so what can i do?
Click to expand...
Click to collapse
Charging would be an excellent option !
athanaso77 said:
Every owner of P3300 has this installed
Click to expand...
Click to collapse
not every.....i don't use it
petervbeck said:
not every.....i don't use it
Click to expand...
Click to collapse
Everytime I feel my Artemis needs an Overclocking - I give it a ROM straight up its slithery USB Hole !!!!
hee hee hee !
Look, just configure your ARTEMIS BatteryStatus,CpuScalar for 120, 201, 247 with this configuration your battery last for ever because when it doesnt need speed goes to the lowest speed, only if you are running aplication the overclock take action.
Hope it helps,
Cheers,
agfsilva said:
Look, just configure your ARTEMIS BatteryStatus,CpuScalar for 120, 201, 247 with this configuration your battery last for ever because when it doesnt need speed goes to the lowest speed, only if you are running aplication the overclock take action.
Hope it helps,
Cheers,
Click to expand...
Click to collapse
Thats cool, thanks!
If you can avoid it, don't overclock!
As stated earlier in this thread...
I've found that overclocking, even with scaling, seriously affects battery performance.
I was until today running Vanilla 2.0, which was ok until I added batterystatus, with either fixed or scale doverclocking - both of which drained the battery like crazy.
If battery status is an isuse, use a lean, clean rom and don't load up loads of stuff you don't need - then the device will perform faster... I've just switched back to the Dopod WM6 release, and unclocked it runs everyhting I need absolutely fine.
To me, overclocking is like the salad bar in Pizza Hut.... I ain't going near it!
TangerineTractor said:
To me, overclocking is like the salad bar in Pizza Hut.... I ain't going near it!
Click to expand...
Click to collapse
lol, thats good! Fair point, I'll keep an eye on the battery life.
Perhaps changing the max speed to the standard speed, but keep the low idle speed set will improve power consumption?
John Boy said:
lol, thats good! Fair point, I'll keep an eye on the battery life.
Perhaps changing the max speed to the standard speed, but keep the low idle speed set will improve power consumption?
Click to expand...
Click to collapse
I think you're probably better off just not installing stuff you don't need, and where posisble install to your SD card, keeping RAM as free as possible - that will give you a cleaner machine and reduce the need to be tempted to consider trying to overclock... make sure that you have low standby and backlight off settings when on battery use, and keep your device on charge overnight so you always have a devcent level of charge in the morning. If you need to, buy a desktop charger from ebay for a few quid, and stick your phone on it when you get home...
TangerineTractor said:
I think you're probably better off just not installing stuff you don't need, and where posisble install to your SD card, keeping RAM as free as possible - that will give you a cleaner machine and reduce the need to be tempted to consider trying to overclock... make sure that you have low standby and backlight off settings when on battery use, and keep your device on charge overnight so you always have a devcent level of charge in the morning. If you need to, buy a desktop charger from ebay for a few quid, and stick your phone on it when you get home...
Click to expand...
Click to collapse
Thanks for the advice. The CPU clocking is being done with Battery Status, which is part of the ROM, so If power consumption continues to be a problem I'll disable the over-clocking function from the Battery Status Options.
As for charging I'm fine, I have an in-car charger and a 40 minute commute every morning/evening
Thanks again,
John
i've got a question about batterystatus, maybe some1 in this post knows the answer:
is there a way that batterystatus keeps the overclock setting while suspended? i would love to UNDERclock my cpu to 123mhz when suspended, so safe extra battery, but seems that everytime i suspend, BS sets it back to 201.
i tried the options, but i can't figure out if it's possible to over/under clock while suspended.
Have you tried the CPUScaler option? It's build in to version 1.04
For the original FAQ etc goto the BatteryStatus website. Or read more in this thread.
i haven't try it. i have artemis 2.2
TangerineTractor said:
I think you're probably better off just not installing stuff you don't need,
Click to expand...
Click to collapse
Well, although I can't uninstall the battery bar I have disabled the over clocking! I sat yesterday and could almost watch the power drain in real time, even with the Max speed set to 201Mhz. I switched the function off and the battery is lasting a lot longer again.
Moral: Don't over-clock at all!
John Boy said:
Well, although I can't uninstall the battery bar I have disabled the over clocking! I sat yesterday and could almost watch the power drain in real time, even with the Max speed set to 201Mhz. I switched the function off and the battery is lasting a lot longer again.
Moral: Don't over-clock at all!
Click to expand...
Click to collapse
I've tried ALL the cooked ROMS here - I have a 'spare' device for testing...
I use my device for work emails, sat nav, personal mails, web browsing, music, and as my phone. I pair it up with a Sony Blootooth car stereo.
So... aside from a few games, what else do you need to do with your phone? I'd suggets that most of the stuff loaded onto some of the ROMS is completely superfluous and just clogs up the device - things like the touch cube are really tarty overheads. Over the past year, I have played with most stuff that's out there, free and paid, and have a pretty default set of standard stuff that I load onto a clean RM. I was using Vanilla 2.0, but that still ate battery, so when I read that the Dopod shipped WM6 ROm was fast and bare, I thought I'd give it a go, and I haven't looked back...
Here's what I have on it, all running from the Stoarage Card where possible:
CloseAll
Hibernate
Hbutton
TodayAgenda (enhanced Calendar on Today)
Sunnysoft Contacts (one fingered dialling in the car)
TotalCommander
TomTom 6
Coreplayer (gives far better bluetooth audio streaming, and plays videos)
iphone keypad (default one buttons too small in the car)
SamsungTime (big clock on Today, but doesn't have the weight of HTC)
With all of this, I get brilliant battery life and a more than adequate response time without any overclocking, and over 20mb useable ROM.
TangerineTractor,
Why have you choosen the Dopod WM6 rom?
After having that rom I switched to the official Europe WM6 rom. No big differences, but with Ms Office 2007 on board, now the Word and Excel files are fully compatible with my desktop PC. The only disadvantage was that I had to install AudioManager separatelly. (But, in fact, I rather use CorePlayer.) It's a stable and reasonable fast rom. Storage Memory is low but each prog is in Storage Card if applicable. And there is very low RAM leaking (after a day of usage it's still above 20 M -- and Spb Mobile Shell runs constantly!).
Have you tried the Europe ver.?
ctibor said:
TangerineTractor,
Why have you choosen the Dopod WM6 rom?
After having that rom I switched to the official Europe WM6 rom. No big differences, but with Ms Office 2007 on board, now the Word and Excel files are fully compatible with my desktop PC. The only disadvantage was that I had to install AudioManager separatelly. (But, in fact, I rather use CorePlayer.) It's a stable and reasonable fast rom. Storage Memory is low but each prog is in Storage Card if applicable. And there is very low RAM leaking (after a day of usage it's still above 20 M -- and Spb Mobile Shell runs constantly!).
Have you tried the Europe ver.?
Click to expand...
Click to collapse
The Dopod WWE ROM from the Wiki link has Office Mobile on it, and to be honest, I hardly use that anyway... which do you mean by the Europe version - maybe I'll give it a blast..??

[Android General] Android Tips & tricks (UPDATE 14/03/10) HUGE UPDATE! 3 uselful tips

[Android General] Android Tips & tricks (UPDATE 14/03/10) HUGE UPDATE! 3 uselful tips
I have fought that the Android/Blackstone community would be happy to learn some tips and tricks to enjoy their configuration better.
You can post yours for sure
TIPS AND TRICKS:
1) Do you find your XAndroid build very slow and not as responsive as you expected ?
Install CleanRAM under WinMo (6.x), set it to "Level 3" (Fundamental Purge). Normally, your build will be faster and more responsive, it works for me !
Feel free to post your feedback
2) Do you find your battery life is not at least good ?
Disabling Wi-Fi toggle can be useful, even if you aren't connected to your favourite Network, let it drains the battery faster than everything...
3) An other battery tip ! Disable Animations in Settings Menu.
It won't change important things, it's almost unnoticeable.
4) You don't use the 3G network ? Disable this option into the comm manager under WinMo 6.x , you'll notice an important changing as regards your battery life
5) Have you found an app which doesn't fit the whole screen ? Open STARTUP.txt and try to change lcd.density from 220 to 240.
(Thanks Slaming)
6) Many many users don't manage to answer their incoming calls. Last night i found a trick. Don't use your finger, but press a bit hard the green circle on your screen with your stylus (no risk for your screen), you'll be finally able to answer your calls !
7) I just found a PERFECT package: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100215_000813.tar
If you don't know how to use it, there are some FAQs
8) Do not forget that your WinMo settings matter !
(Especially Screen settings, comm manager settings, etc, i'll give more details soon)
9) How to install glemsom's packages according to Slaming:
"to install this just download the zip and place it in your sd card then edit the starup and change zimage to the name of the zimage you are uing so in this case it will be zImage-20100215_000813 when its booting you will see the kernel script and it will say new image or something. hope this helps.
and dont forget don't unzip the other file inside the original zip just place it in the sd card normally."
10) I think i have found a temporary fix as regards DEEP SLEEP ISSUES (I test it for three days and the conlusion is impressive !).
There are the instructions:
1) Download the app SetCPU (included in Glossy's packages)
2) Install the app via the market (if you've downloaded it via your phone) or Astro file manager (If you have the .apk)
3) Launch SetCPU and choose "Auto Detect" (at the end of the list)
4) Set Max at 528MHz and Min at 245MHz, enable "Set on Boot" and let CPU Governor as "On demand"
5) Exit the app, test my tip and leave your feedback
Warning: Your battery life won't be shorter, don't worry.
11) Your Network drops down sometimes and never reappear ? Select your network manually, and if it doesn't work, don't reboot, it can take some time
I'm french so i do: Paramètres (Settings) => Réseaux sans fils (top of the list) => Paramètres réseaux mobiles (bottom of the list) => Recherche manuelle (Manually search ?), wait 10 sec and select your favorite network.
12) Boot failed to mount sd card ? Try this: http://groups.google.com/group/beagleboard/browse_thread/thread/ef88a97aaef9116b?pli=1
13) Tired of installing all your APKs ? Just put your precious APKs in "Androidapps" folder, it will auto-install apps when booting. Thanks Brodos123
14) Deep Sleep problems are getting on your nerves ? Try to use the "board-htcblackstone-panel.no_bkl_off=1" in the cmdline in startup.txt. Thanks Brodos123
15) Tired of seeing all this "fsck0001", "fsck0002" ? You can delete them without having any issue ! Thanks N!ghty
16) Want to use your personnal wallpapers ? Try to put your JPEG, or GIF, or any image file into sdcard\media\resource\ , and select one of them with your favorite wallpapers manager. Thanks N!ghty
[11/02/2010] Update !
[13/02/2010] Update ! Thanks Slaming
[14/02/2010] Update !
[16/02/2010] Update ! [Perfect Glemson Package added !]
[17/02/2010] Update ! [Warning about WinMo Config]
& How to install Glemsom's packages (thanks slaming).
[19/02/2010] Update ! DEEP SLEEP ISSUES ALMOST FIXED !
[27/02/2010] Update ! Fix for when the network drop down.
[05/03/2010] Update ! "Failed to mount sd card" fixes.
[13/03/2010] Update ! How to auto-install all your APKs.
[14/03/2010] Update ! HUGE UPDATE ! (3 new useful tips) Thanks Brodos123 and N!ghty.
finding apps aren't taking up the whole screen open the startup txt and change lcd.density from 220 to 240
WinningDays said:
TIPS AND TRICKS:
1) Do you find your XAndroid build very slow and not as responsive as you expected ?
Install CleanRAM under WinMo (6.x), set it to "Level 3" (Fundamental Purge). Normally, your build will be faster and more responsive, it works for me !
Feel free to post your feedback
2) Do you find your battery life is not at least good ?
Disabling Wi-Fi toggle can be useful, even if you aren't connected to your favourite Network, let it drains the battery faster than everything...
3) An other battery tip ! Disable Animations in Settings Menu.
It won't change important things, it's almost unnoticeable.
4) You don't use the 3G network ? Disable this option into the comm manager under WinMo 6.x , you'll notice an important changing as regards your battery life
5) Have you found an app which doesn't fit the whole screen ? Open STARTUP.txt and try to change lcd.density from 220 to 240.
(Thanks Slaming)
6) Many many users don't manage to answer their incoming calls. Last night i found a trick. Don't use your finger, but press a bit hard the green circle on your screen with your stylus (no risk for your screen), you'll be finally able to answer your calls !
7) I just found a PERFECT package: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100215_000813.tar
If you don't know how to use it, there are some FAQs
Click to expand...
Click to collapse
How is the wake up on sleep problem in this kernel?
No problem for me It should be the same for you.
The same sleep problem. Put the phone into sleep mode and leave it in your pocket for 15 minutes and see.
There hasn't really been any notable progress as far as fixing what is broken on Blackstone (or any of the features that don't work like camera, bluetooth, etc.) since December.
If you've been following the notes on the zimage builds, you'll see how slow progress really is. Although I appreciate how difficult it is for those working it, I think they'll still be working on it long after we've upgraded to another a phone, and with what they're up against, I wouldn't hold my breath about getting new features to work.
Besides, HTC Bravo/Desire will be available in March... Snapdragon? new Sense UI? Yes please.
I've woken up my device about 500 times and this problem have appeared only 2 or 3 times.
WinningDays said:
TIPS AND TRICKS:
7) I just found a PERFECT package: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100215_000813.tar
If you don't know how to use it, there are some FAQs
Click to expand...
Click to collapse
to install this just download the zip and place it in your sd card then edit the starup and change zimage to the name of the zimage you are uing so in this case it will be zImage-20100215_000813 when its booting you will see the kernel script and it will say new image or something. hope this helps.
and dont forget don't unzip the other file inside the original zip just place it in the sd card normally.
what do you mean by "perfect"?
how perfect it is and in what aspect?
It is meaningless to say perfect with no content at all.
Perfect for what we have at the moment
BT, headphones and camera still doesn't work, but this package make Android smooth, fast, wifi works perfectly, 3g too, and i didn't have any trouble with deep sleep
WinningDays said:
Perfect for what we have at the moment
BT, headphones and camera still doesn't work, but this package make Android smooth, fast, wifi works perfectly, 3g too, and i didn't have any trouble with deep sleep
Click to expand...
Click to collapse
Leave it charging over night in sleep mode, then try and wake it up. Doesn't work.
Although this is an overall good package, it suffers the same current bugs that have yet to be resolved. Every zimage build has had this problem since they added sleep functionality last month, and unfortunately its marked as a 'low priority' bug in the forum.
I leave my phone charging every night when android is booted and i have no problem.
on Diamond?
Can i put this on Diamond? afaik, it should go, since I am only replacing the zImage.
re-Posted: http://forum.xda-developers.com/showpost.php?p=5662770&postcount=74
mod may delete....
You'd better post in the Android Questions for this, put i'll try to answer your question.
I think you can only put modules and zImage, but i'm not sure...
sraaj said:
Can i put this on Diamond? afaik, it should go, since I am only replacing the zImage.
re-Posted: http://forum.xda-developers.com/showpost.php?p=5662770&postcount=74
mod may delete....
Click to expand...
Click to collapse
all of these builds are generic the only that changes is the startup hope this helps
Update concerning Deep Sleep issues
WinningDays said:
Update concerning Deep Sleep issues
Click to expand...
Click to collapse
doesnt work for me... at all
WinningDays said:
Update concerning Deep Sleep issues
Click to expand...
Click to collapse
Hey!
Tottaly worked for me.
Using glossy 1.7 and had sleep problems before.
used SETCPU and worked.
Thanks.
Left charging all night and today it woked up from sleep.
Never did this before.
Worked for me too!
Testing it for two days and didn't had one sleep problem.
Keep up the good work!

mssmison did it!: CyanogenMod 5.07 test 3. for kaiser!

wifi working with patch.
http://forum.xda-developers.com/attachment.php?attachmentid=325161&d=1273647492
http://forum.xda-developers.com/showthread.php?t=679680
could someone resize it to 240x320 please? cant wait to try this
Heads up! New Kaiser Wifi update: http://forum.xda-developers.com/showpost.php?p=6456191&postcount=33
Old one replaced build.prop with wrong version. Reinstall and use the new Wifi update.
Also to get rid of android-rebooting-problems with GPS Test application do the following:
1. Start terminal emulator
2. su
3. cd system/lib/hw
4. rwsystem
5. rm sensors.msm7k.so
6. rosystem
7. exit
8. exit
9. restart phone
So how is it? I'm too lazy to install it.
Dukenukemx said:
So how is it? I'm too lazy to install it.
Click to expand...
Click to collapse
Seems like a really nice build. I'm using 320x428 with 144 dpi. A bit slow because I'm currently not running in NAND but I would expect it to perform quite well once I go back to running NAND again.
I haven't tested it very much yet as I'm doing some experiments in WinMO at the moment.
just tried
hey
i just downloaded this and i have to say im impressed about this.
as i love the eclair design and everything and the donut speed i have to say this is impressing because it is FAST! not as fast as donut but pretty much the same. that could be due to the 500 mHz OC but i just like that build.
just needs to be optimized a bit, maybe a few apps like astro and others
and as the developer has a new phone we need a new one.
But i have to say its awesome!
i love it already and just tried it for 9 min.
just the OC needs to be removed i noticed right now and is there any way to set another value for the screen sensebility because quiet often it does not react on a touch.
so keep updating this!
nick
nice rom but it chews through battery like crazy. With a full charge battery will drop from 99 to 75(battery fix removed OC and set 1400 value) with just a 10min phone call and a couple txts. I think what we need is a new kernel highly optimized for battery life using the latest patches. Judging from the name alone of the kernel its running right now 2.6.25-01051-gc362ac-dirty and the fact that 2.6.25 was released in jul 2008 i think theres room for tons for improvement.
Does anyone know how to adjust the microphone gain? my friends complain they cant hear me..
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
kallt_kaffe said:
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
Click to expand...
Click to collapse
Thanks to update.
It working good on Polaris.
Also i change interval to 180 and density to 120 in .prop
Here's an update that changes the wifi scan delay to 120 seconds and also (not tested yet) changes the model name from Vogue to Kaiser.
i'm still trying to figure out if it's possible, somehow, to flash an update.zip file (to be able to use the cyanogenmod skins) with the nomorootfs we're using, instead of converting the skins to metamorph format
does anyone know if it's possible or how to do it?
Can't get wifi to work with updates, which one should I need?
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Dukenukemx said:
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Click to expand...
Click to collapse
edit: how stupid can I be? I've bought another phone and forgot to add the mac adress.
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
mssmison didn't say he was going to put any more effort into it either. Hopefully, someone will pick it up.
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power.
Click to expand...
Click to collapse
Try deleting /data/system/batterystats.bin. That usually helps when the batterymeter has gone bad.
A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
kallt_kaffe how do you do it?
I'm new to the androidinstall.tar method. I'm tyring to run from haret but it seems impossible.
You said you where experimenting with something in winmo, so that implies you're using haret? Are you running from haret?
When I try, Polymod, and Mssmission they don't show an install option, when I try myn and incubus I get it installed but I get no sound. It was actually your gps kernel that let me get things installed all other kernels i tried had non-functional dpads within the installer environment. Also, trying another kernel once installed didn't fix the sound issue.
Anyhow just let me know if you're using Haret. I wonder whats up with the sound and missing install option. I tried the install two different ways one with a 2gb fat32 partition, and then another attempt using three primary partitions 1.3gb fat32, 300mb ext, 300mb ext. All installers then would give me options beside's fat, but not all intallers would have an install option.. I'm using radio 1.71.09.01.eMo, model: kais100, os: wm6.5 (shifu v.3)
kallt_kaffe said:
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
Click to expand...
Click to collapse
I try start Skyforce game, but it forceclose.
It can work after i added "sensors.sapphire.so" into /lib/modules/hw/
I've installed the cyanogenMod updater from the marketplace, but it can only find older versions, no experimental versions, whatever option I set in the program.Anyone?
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
battery life has been fantastic for me on this build...
although I reverted back to 400mhz and got rid of compcache.
I am sure that OCing to 500 by default is draining the battery faster.
I would rather a usable phone than a fast one...(although it still seems very fast to me)

[Q&A][UNOFFICIAL] CyanogenMod/LineageOS

Q&A for CyanogenMod/LineageOS for Celox Devices (Hercules & Skyrocket)​
As requested I created a Q&A thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by me.
Before posting, please use the forum search and read through the discussion thread above for your device. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Frequently Asked Questions​
Q: My device reboots when I receive or make a phone call. Why?
If your using OpenGapps read this: https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Click to expand...
Click to collapse
Q: Formatting my SD Card as Internal Storage doesn't work. How to fix it?
Goto Settings > Storage. Click on your external sdcard
Tap the Menu button in the top right and select Settings.
Then choose Format as internal. (This erases all the data on the sdcard so backup if necessary)
Once you click Erase & Format, the device will format your card.
The process may get stuck at 20% and timeout after about 2mins. If it does reboot into recovery after it times out.
In TWRP, select Wipe then Advanced Wipe. Select "MicroSD Card - Data" and click "Repair or Change File System".
Choose, "Change File System" and select FAT. Then swipe to change.
Reboot, then goto Settings > Storage. Your sdcard should appear as corrupted.
Continue and format as internal storage. It should then get past 20%. If it does, continue with the steps shown to you.
Click to expand...
Click to collapse
[FONT=Arial,Roboto,Helvetica Neue,Helvetica,Verdana,sans-serif]Frequently Asked Questions[/FONT]​
Since this is a unified thread, I will use Celox to refer to both the Hercules and the Skyrocket. This was their planned codename for the LTE S2, and both use the celox-common branch in source code.
Q: How do I root my Celox? I flashed SuperSU, and my phone won't boot!
A: You don't need SuperSU. Root access is baked into the ROM.
Wipe everything and install the ROM without SuperSU. Now, in Developer options, set Root access to Apps and ADB. If you really, really, want SuperSU, install it from the Play Store and have it install it directly without recovery. (not confirmed working, but should work.)
Q: Do I install this like any other ROM? Why can't I install Gapps?
A: No. This is a virtually partitioned ROM, common in today's Celox ROMs. The different partition layout is necessary to take full advantage of your phone.
Q: Clean flash or dirty flash?
A: I always dirty flash. I never wipe unless I am switching ROMs. You may want to wipe, your choice.
Q: Virtual repartition? Whaaaaaat? Do I need a PIT file? Will this damage my device?
A: The classic issues with the S2 are:
Not having enough room to install apps
Being forced to use tiny Gapps packages
having waaaaaay too much internal sd card free space, even when you have a real SD card that you haven't filled up either.
Virtual repartitioning changes the way the system sees the partitions ("sections" of the 16GB of storage), making it similar to the 16GB Samsung Galaxy S3. This fixes all of those problems!
Here is what happens:
To make more room for apps and data, we made that SD card partition multitask as apps, data, and the internal SD card storage, emulated at /data/media/0, like modern devices. This will wipe those files on the internal SD card partition, though! You now get 11.2GB freely usable by the system.
Since Lollipop, ROMs have been increasing in size greatly. They even use a different installation method. Our measly 598MB /system partition, which couldn't even hold all of 4.1.2 TouchWiz, has been moved to what /data was before. That means 2GB for the ROM, Gapps (yes, you can even flash STOCK!), BusyBox, root stuff, extensions, you name it!
And that 598MB /system partition becomes /cache, because you can always have more cache!
No PIT is needed, and, if you flashed a PIT (like the one that gives you 6GB for data), flash it back to stock! You will end up with 7GB shared for the internal SD card and app data and 6GB for /system, which is ridiculous.
And the best part is: Nothing is damaged. It is 100% safe! It is just a renaming scheme, and you can always flash to stock in Odin.
Q: Which Gapps should I use?
A: Well, as always, it is your decision, so so as you wish. I personally use Nano, which I also recommend. However, you need to install keyboard_patch.zip (attached to this post) after a Full or smaller Gapps or you will get spammed by "Unfortunately, Android Keyboard (AOSP) has stopped.", making it impossible to set up your device.
Stock fixes this issue, but it also adds crapware that I bet you don't need, like Google Sheets, Google Maps, Google+, and especially Chrome.
Q: HALP!! I'm getting "Unfortunately, Android Keyboard (AOSP) has stopped.", I can't set up my phone, and I am about ready to throw this thing at the wall!!!!!1!
A: Calm down. Breathe. I know it is annoying and gives you headaches.
Just reboot into recovery (using the key combo), and flash keyboard_patch.zip, attached to this post.
Q: Whenever I browse the web in Chrome, my phone goes berserk! It slows down, shows me black screens then the lockscreen, etc.
A: Don't use Chrome. The stock browser is about as good and doesn't wreak havoc to our device. However, this is replaced when you flash a larger Gapps package. I recommend using Nano and installing what you want instead. Just wipe system, flash ROM, Nano, keyboard_patch.zip, and reboot. Alternatively, you can use Opera, which has everything Chrome has except Google account bookmark sync and bloat.
Q: I have one of the following issues:
Calls don't work. They reboot or say "Cellular network not available."
When I turn on my device, I don't have a data connection.
A: You flashed the wrong build. Flash anything after 20160126 and those issues are fixed!
Q: My battery life is bad.
A: Here are some general tips I use:
Turn data, WiFi, GPS and Bluetooth off when you are not using them.
Understand that lower signal = shorter battery life.
Settings > WiFi > Menu > Advanced > Keep WiFi on during sleep > Only when plugged in.
Settings > WiFi > Menu > Advanced > Always allow scanning > Off.
Black wallpaper = good.
Underclock/undervolt.
Lower brightness to the minimum you can see.
Enable the Power saver profile (currently not working on 2/16).
Install the blacked out // regression+ theme, which makes most things black. Pure black = good.
If you really want to stretch your battery life, you can do these extreme tweaks, however, they can affect the functionality of your phone.
Green-only mode. It looks pretty awesome and saves battery life. In terms of battery life, AMOLED screens get better battery life depending on the color displayed on the screen. Green > Red > Blue. Black uses almost no energy.
Set to blacked out // regression+
Black wallpaper
Brightness to 0%
Settings > Developer options > Simulate color space > Monochromacy. This makes it so you can (mostly) see non-green colors.
Settings > Display > LiveDisplay > Color calibration and set all but green to 0%.
Download [root] Naptime (with root enabled) and enable the Aggressive Doze mode. Your phone will be practically off (only the cell radio with data off is running) and you will not receive most notifications, sans phone calls, text messages, alarms, and seriously important notifications as soon as the screen turns off. This is also naturally enabled when you leave your phone unplugged and not moving for 30 minutes.
Hold down the power button and select "Power off". This is a feature that causes your phone to use absolutely no power, however, your phone will take about a minute or two to exit this mode and you will not receive any calls, notifications, texts, or anything and WiFi, mobile networks, Bluetooth, GPS and the CPU will be disabled during this mode.
Q: After 30 minutes of my phone's screen being off, WiFi turns off. I just can't seem to shake this bug!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is called "Doze", it is a built-in feature added in Android to attempt to save battery. Jerry Hildenbrand did a good job explaining this at Android Central.
You can configure this using [root] Naptime, but it is a rather advanced tool.
Q: My keys stopped working! What did I do wrong?
A: Disable Sweep2wake in the "Advanced Settings" app. That tweak is cool, but not yet stable enough for daily use.
Q: How do I make things smaller?
A: Settings > Display & lights > LCD density.
Thankfully, they fixed the alignment bug, so you no longer need to edit your build.prop.
The larger the number, the larger things will be, and the smaller the device will identify as.
240 is the default. The 4.5 in (11.43 cm) device is recognized as a measly 3.89 in (9.87 cm). Friends don't let friends stay on 240 DPI.
Technically, the Celox has a DPI of 207, but apps work best with multiples of 20.
I personally recommend 200dpi, which makes the device identify as 4.66 in (11.85 cm). It is quite nice.
However, with a non-standard DPI (standards are 120, 160, 240, 320, 480, and 640), it can cause scaling issues like blurriness.
Q: Should I use EXT4 or F2FS?
A: I use F2FS. F2FS is safer for your data, writes faster, and is actually designed for flash memory (it is called Flash-Friendly File System), unlike EXT4, which is made for a hard drive. However, some people encountered issues with F2FS and the Play Store.
EXT4 is tried and true, and is still relevant.
Q: Why does my camera keep crashing?
A: In the Advanced Settings app, check "Force low-power flash".
Q: I get random reboots. I see the Samsung logo, then a black screen! Grr!
A: At the time of this writing, 1/26 (sometimes 1/27) is the most stable. Try flashing that.
Q: How do I remove the pesky # on the status bar?
A: Install this Xposed module, or it is also a part of this all-in-one tweakbox by the same developer.
Q: Are there any cool features in this ROM/Kernel?
A: Yes, there are more features in this than the usual CyanogenMod Celox kernel. Some features are still being worked on and are a bit unstable, but testing and fixing is welcome on our GitHub repo!
We have, so far:
Wake/Sleep:
sweep2wake
doubletap2wake
doubletap2sleep
pocket detection (enable in Kernel Adiutor)
Click to expand...
Click to collapse
Miscellaneous:
Backlight notification (the keys light up like the LED indicator we never had)
F2FS support
Screen undervolting to -500mV
Low-power flash
zRAM (compressed RAM)
Magically added more RAM: Now we have 834MB.
Click to expand...
Click to collapse
CPU general
Overclock to 1.83GHz
Under/Overvolting
A democracy of governors (see below)
GPU can be overclocked to 320MHz
Click to expand...
Click to collapse
CPU Governors:
Bold are considered (mostly) stable.
hyper
badass
conservative
gaming
interactive
interactiveX
lazy
lionheart
minmax
ondemand (the default)
performance
powersave (though this just locks at the minimum frequency)
sakuractive
samsung
scary
smartassV2
uberdemand
userspace
wheatley
Click to expand...
Click to collapse
I/O Schedulers:
bfq
cfq
deadline
noop
row
Click to expand...
Click to collapse
If you want more, request it!
Or... even better, contribute to the kernel on Github.
Q: Why can't I configure my CPU governors?
There was a bug in the 2/16 build that added governors, but they had issues with case-sensitivity. Flash 2/22 or newer and you get governors and configuration.
Q: When will we get an update?
A: Be patient! Or build it yourself. Don't forget that some people have lives, and some people don't have lives but still aren't going to constantly update.
I will update this with more questions and answers.
Please don't quote this whole thing. Just mention @Easy_as_Pi_3.14 and I should respond quickly. Or don't, I am subscribed to this thread and love to answer questions.
Easy_as_Pi_3.14 said:
Q: My battery life is bad.
Sorry, this isn't the best ROM for battery life. That hasn't really been hammered out yet.
However, here are some general tips I use:
Turn data, WiFi, GPS and Bluetooth off when you are not using them.
Black wallpaper = good.
Underclock/undervolt.
Lower brightness to the minimum you can see.
Enable the Power saver profile (currently not working on 2/16).
Install the blacked out // regression+ theme, which makes most things black. Pure black = good.
If you really want to stretch your battery life, you can do these extreme tweaks, however, they can affect the functionality of your phone.
Green-only mode. It looks pretty awesome and saves battery life. In terms of battery life, AMOLED screens get better battery life depending on the color displayed on the screen. Green > Red > Blue. Black uses almost no energy.
Set to blacked out // regression+
Black wallpaper
Brightness to 0%
Settings > Developer options > Simulate color space > Monochromacy. This makes it so you can (mostly) see non-green colors.
Settings > Display > LiveDisplay > Color calibration and set all but green to 0%.
Download [root] Naptime (with root enabled) and enable the Aggressive Doze mode. Your phone will be practically off (only the cell radio with data off is running) and you will not receive most notifications, sans phone calls, text messages, alarms, and seriously important notifications as soon as the screen turns off. This is also naturally enabled when you leave your phone unplugged and not moving for 30 minutes.
Hold down the power button and select "Power off". This is a feature that causes your phone to use absolutely no power, however, your phone will take about a minute or two to exit this mode and you will not receive any calls, notifications, texts, or anything and WiFi, mobile networks, Bluetooth, GPS and the CPU will be disabled during this mode.
Click to expand...
Click to collapse
I have to differ with this point. As I have said many times in the main thread, my battery life has been awesome. I have a healthy battery. You have stated that your battery is nearly dead and that you jump through these hoops to get it to last.
I post this so that people who see this don't think that this rom is bad for battery life. It's not, if you have a healthy battery. Here are my current settings:
Screen always on Auto Brightness
Wifi Always on (even when connected to Data)
Sync is always on
NFC off
BT off
I use data about 25% of the time
When on Data I have location set to battery saving
I use the Balanced battery setting
I make all my calls through Hangouts
I have dozens of apps installed
I am using Rom V. 1/26 (dirty flashed)
My average battery life right now is about 24-36 hours with 1.5-2.5 hours of Screen on Time. And my battery charges from about 10% to full in about two hours. My best battery life so far has been about 49 hours with 1.25 hours of SOT before needing to recharge. My average Doze usage is about 1.5%/hour- this is without tinkering with Doze settings with an app.
This battery life is on par with newer devices.
edit. Here is a screenshot of my battery usage right now. Nearly two days and this is with about 1 hour of SOT
cameraddict said:
I have to differ with this point. As I have said many times in the main thread, my battery life has been awesome. I have a healthy battery. You have stated that your battery is nearly dead and that you jump through these hoops to get it to last.
I post this so that people who see this don't think that this rom is bad for battery life. It's not, if you have a healthy battery. Here are my current settings:
Screen always on Auto Brightness
Wifi Always on (even when connected to Data)
Sync is always on
NFC off
BT off
I use data about 25% of the time
When on Data I have location set to battery saving
I use the Balanced battery setting
I make all my calls through Hangouts
I have dozens of apps installed
I am using Rom V. 1/26 (dirty flashed)
My average battery life right now is about 24-36 hours with 1.5-2.5 hours of Screen on Time. And my battery charges from about 10% to full in about two hours. My best battery life so far has been about 49 hours with 1.25 hours of SOT before needing to recharge. My average Doze usage is about 1.5%/hour- this is without tinkering with Doze settings with an app.
This battery life is on par with newer devices.
edit. Here is a screenshot of my battery usage right now. Nearly two days and this is with about 1 hour of SOT
Click to expand...
Click to collapse
Well,
You had amazing signal 24/7. Damn you, T-Mobile!!!!! (I miss the days of the you-step-indoors-and-you-lose-signal and AT&T users laugh)
1 hour of SOT. Try this: Marathon it. Do a YouTube playlist. Go on a Google Search frenzy.
You were in Doze 95% of the time.
David (not even gonna try to spell his username, too late at night) was also comparing his battery life to 4.4 AOKP. I have always heard that AOKP is amazing on battery life.
Update, here is my battery life. The Doze part was me using my S3 when this was on my bed, and then finally watching The Force Awakens. (PS: Great movie!)
And that is in airplane mode the whole time.
The rest was mostly me web browsing or watching a YouTube playlist.
Sent from my SGH-I727 using Tapatalk
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
tommyguns818 said:
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
Click to expand...
Click to collapse
Nope. There may be Yes, there is an Xposed module for that. See two posts down.
Sent from my SGH-I727 using Tapatalk
Easy_as_Pi_3.14 said:
Well,
You had amazing signal 24/7. Damn you, T-Mobile!!!!! (I miss the days of the you-step-indoors-and-you-lose-signal and AT&T users laugh)
1 hour of SOT. Try this: Marathon it. Do a YouTube playlist. Go on a Google Search frenzy.
You were in Doze 95% of the time.
Click to expand...
Click to collapse
Yeah, I get pretty good signal here. I live in a major city. :good:
But about 8 hours of that was in an area of low signal. Also, my Doze usage was for nearly two days! And I didn't baby the phone. I just used it for messaging/calls/email and a few searches, and my calendar and updating a few apps in that time. When I plugged it in this morning I had hit 48 hours with 1.25 SOT with 4% left. I could have gone another few hours if need be.
My average SOT time is closer to 2.5 hours with about 24 hours standby (Doze). I've gotten as high as about 4 hours SOT with about 18 hours standby. I've already run a high drain test, SOT almost at 100% of the time, it averaged about 20%/hour. So at that rate the device would last for about 5 hours. But that is not average usage. My high usage of 3-4 hours with 18 hours standby is a better metric. And by all standards, this is excellent battery life for a device with an 1800mah battery without battery saving features engaged!
Oh, and my Doze usage last night was at 0.9%/hour
tommyguns818 said:
Great job on this rom. Running great on 1/26. Didn't see it but is there a way to disable superuser icon in the status bar? I saw it for alarm, wifi, etc.... But not for SU. Just curious. Thanks.
Click to expand...
Click to collapse
Yep, there is an Xposed mod for that! Disable su indicator (CM12) or in his all-in-one here.
I updated the Q&A. Thanks for asking that question!
@Easy_as_Pi_3.14 can I call you 22/7's?
You might want to include my video demonstrations of the wake algorithms in the FAQ
https://www.youtube.com/playlist?list=PLZ_n933bbFxFX7UUVjookMDEl1DYShSfg
(Sweep2Sleep and leniency are irrelevant to this kernel)
Also make a note that pocket detection makes wake controls not work when it's sufficiently dark
(My algorithm uses the light sensor data to check if it's in a pocket, YMMV on "sufficiently")
Also, btw, you might wanna make a list of recommended stable governors
IMO Uberdemand seems to be one of them
Further more I recommend putting that f2fs is only for data and cache (or maybe put a guide with how to convert to it)
Also, you are missing a few things in the kernel features that might be good to mention, and maybe explain what they are
Vibration Intensity, TCP Congestion Controls, KCAL, MDP Cooler Colors Control
I'll keep thinking of stuff to add to the FAQ
No doubt it will get bigger and bigger as time goes on :/
javelinanddart said:
@Easy_as_Pi_3.14 can I call you 22/7's?
You might want to include my video demonstrations of the wake algorithms in the FAQ
https://www.youtube.com/playlist?list=PLZ_n933bbFxFX7UUVjookMDEl1DYShSfg
(Sweep2Sleep and leniency are irrelevant to this kernel)
Also make a note that pocket detection makes wake controls not work when it's sufficiently dark
(My algorithm uses the light sensor data to check if it's in a pocket, YMMV on "sufficiently")
Also, btw, you might wanna make a list of recommended stable governors
IMO Uberdemand seems to be one of them
Further more I recommend putting that f2fs is only for data and cache (or maybe put a guide with how to convert to it)
Also, you are missing a few things in the kernel features that might be good to mention, and maybe explain what they are
Vibration Intensity, TCP Congestion Controls, KCAL, MDP Cooler Colors Control
I'll keep thinking of stuff to add to the FAQ
No doubt it will get bigger and bigger as time goes on :/
Click to expand...
Click to collapse
For short, call me @π.
Or, 355/113 will still get my attention.
Governor Explanations
I found this interesting thread about different governors, how they work and how to tweak them. Thought some might find it interesting:
@bryan2894, I noticed that the Show CPU usage in Developer options is blocked by SELinux.
I know it is silly, but here is the message:
Code:
type=1400 audit(1456274524.501:678): avc: denied { search } for pid=743 comm="ndroid.systemui" name="3846" dev=proc ino=31386 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0
Deleted
Deleted
@bryan2894 @javelinanddart
I got a logcat/dmesg of the infamous touchkey derp.
I got it around 6:00.
Sorry about the "MP-Decision" spam.
Couldn't find it, but is there power menu options to add screenshot?
tommyguns818 said:
Couldn't find it, but is there power menu options to add screenshot?
Click to expand...
Click to collapse
It is there already for me.
However, I found it easier to either use the key combo (volume first helps) or downloading an advanced file manager (my favorite), open Now On Tap (long-press Home in virtual keys, Menu or Search if I recall correctly on touchkeys), hit the share button, then use Save as.
Sent from my SGH-I727 using Tapatalk
Easy_as_Pi_3.14 said:
@bryan2894 @javelinanddart
I got a logcat/dmesg of the infamous touchkey derp.
I got it around 6:00.
Sorry about the "MP-Decision" spam.
Click to expand...
Click to collapse
Yeah idk about the logcat (not my forte), but I looked for some touchkey errors in kmsg:
Code:
[19778.598175] [TKEY] tkey_vdd_enable: enter
[19778.598358] tkey_led_vdd_enable 0
[19778.732757] [TKEY] sec_touchkey_early_resume
[19778.732788] [TKEY] tkey_vdd_enable: enter
[19778.732849] tkey_led_vdd_enable 1
[19779.286621] [TKEY] enter touchkey_auto_calibration
[19952.978363] key pressed
[19953.873016] key released
[19958.626525] key pressed
[19959.776763] key released
[19969.971923] key pressed
[19970.642944] key released
[19977.845245] key pressed
[19978.931579] key released
EDIT: @Easy_as_Pi_3.14 What is the touchkey derp btw? I'm clueless about that, never heard of it.
javelinanddart said:
Yeah idk about the logcat (not my forte), but I looked for some touchkey errors in kmsg:
Code:
[19778.598175] [TKEY] tkey_vdd_enable: enter
[19778.598358] tkey_led_vdd_enable 0
[19778.732757] [TKEY] sec_touchkey_early_resume
[19778.732788] [TKEY] tkey_vdd_enable: enter
[19778.732849] tkey_led_vdd_enable 1
[19779.286621] [TKEY] enter touchkey_auto_calibration
[19952.978363] key pressed
[19953.873016] key released
[19958.626525] key pressed
[19959.776763] key released
[19969.971923] key pressed
[19970.642944] key released
[19977.845245] key pressed
[19978.931579] key released
EDIT: @Easy_as_Pi_3.14 What is the touchkey derp btw? I'm clueless about that, never heard of it.
Click to expand...
Click to collapse
Sweep2wake sometimes makes the touchkeys stop working.
Sent from my SGH-I747 using Tapatalk
Easy_as_Pi_3.14 said:
Sweep2wake sometimes makes the touchkeys stop working.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hmmm... I've had that before as well, but I do not recall having it on hercules (although I'm on CM11)
I had it on T769 (Candy 5.1)
So maybe it's a LP+ Issue?
Does anyone remember having it from before LP?

Thermal Daemon Mitigation OFF with CM?

Dear All,
I´ve managed to build a CM 12.1 with nfs support. Why 12.1? Well, for my D855, that was the only branch I could get working when building a kernel in Ubuntu, using the downloadable snapshot at CM´s site. The nighty´s would give me errors of different kinds during the building process, so the files on the phone needed when building are probably not the exact required version that match with the repo you can download in terminal mode.
Anyway, my experience with marshmellow is that the phone gets so hot that it turns itself off - another good reason to stay with 12.1.
My phone however still gets hot, which happens when using it with my VR headset to watch UHD clips. After 5 mins of watching, it dims down a bit. Then a few mins later a bit more, and so on until it looks like I´m staring at the screen through old cheap shades.
I´ve already disabled automatic brightness control, tried apps which claim to keep the brightness at the desired strength (Lux, the app is called), an app that´s ment to keep the screen always on (Always Awake), an app claiming to patch this exact bug, flashed a hack that´ll throttle only above 70 C. None of this helped. What I do know is that in the secret menu of stock firmware, there´s an option called Thermal Daemon Mitigation OFF, but I can´t access the secret menu through CM - only CM´s secret menu, that doesn´t have this option. Enabling this is said to cope with the problem.
There´s also a file named thermanager.xml in system/etc, which looks like something which can be modified to meet my requirements, but I´m not sure.
Finally, my least prefered option is to install a thermal pad on the SoC, but although I´m experienced with hardware, it´s on desktop level - not with such tiny things as a mobile.
So please, could someone help out here? Is there a way to rebuild the kernel with the stock secret menu or amendments to the throttling? Is there a way for me to get into the stock secret menu in CM?
Other ideas?
PS: I´m posting here because if there´s a way to get Thermal Daemon Mitigation OFF option related parameters set when building kernel in menuconfig, then it´s related to this sub forum.
PPS: Edited thermanager so all brightness values are 255, this seems to fix the problem!

Categories

Resources