[Q] Kernel Fails To Boot With Increased Version In Makefile

[Q] Kernel Fails To Boot With Increased Version In Makefile - Fascinate General

I have been woeking on a custom kernel I will be releasing shortly but I am having a problem with it. Everything works great with it but when I change the kernel version # and attempt to boot it freezes at rhe samsung screen. I tried insmod -f and compiling with modversions enabled and it continues to freeze and I do not know how to pull a /proc/kmsg during a failed boot to find out as adb does not appear to be active. I suspect a module is barfing at the higher kernel version #. Anyone have a suggestion?

Don't change it.
Its a problem several have had, but with no clear solution yet.

Solution found
Hex edit binary modules from samsung with current required source version...not kosher but it boots and plays well with others. Use my soon to be released kernel as an example.

Related

[ROM] Acer AV041 1.31.00 WW GEN1 w/ Root and Busybox [May 18, 2012]

Rom (Ice Cream Sandwich):
A Near stock image, modified for a clean root, busybox install
ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
(MD5: 7e9fe5642b6e082fb4382288337d8dfa)
The long overdue update to my previous Honeycomb rom
==~== Requirements ==~==
This rom requires the unlocked ICS bootloader, I also recommend my A500 Public Recovery, however all recoverys patched for the new bootloader ought to allow installation of the rom.
Bootloader install instructions are: here thanks to civato. Note for step 4 simply ensure my update zip above is either in on the device instead of the ones listed. Note instructions below before actually flashing the rom.
Additional information can be found at Skrilax_CZ's bootloader development thread here
And my A500 Public Recovery development thread here
==~== Installing ==~==
Once you have the new bootloader and ICS recovery installed (again preferably the A500 Public Recovery but any ought to work)
Cleaning your tablet:
If you are attempting to upgrade the tablet without wiping (and there is no need to wipe if you are currently running my acer7.014.14 rooted image
Select "cleanup tab" in the main menu of the A500 Public Recovery
(If you are using another recovery, select the options for a. Wipe Cache, b. Wipe Dalvik Cache, and c. Fix Permissions)
Install the rom:
Select "install zip from sdcard" and navigate to ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
Thats it
==~== Root ==~==
Applications are granted Superuser access from ChainsDD's Superuser.apk as usual (a request asking you will appear when an application requests root, and permissions granted before the upgrade may still be active post upgrade)
adb shell: ADB by default will not have root access here you have the following options:
> if you run 'adb root' all adb operations will have root until reboot (aka 'adb shell' and 'adb remount')
> If you have a non-root 'adb shell' you can switch to root with the 'su' command
> If you wish to restore the permanent adb root on boot add the following line to the build.prop 'service.adb.root=1' this will force the old behavior of root always via adb without using the 'adb root' command.
This change has been made as its a little more secure, (However obviously still lets anyone with access to the USB port access to all the tablets data)
==~== Features ==~==
This rom is intended for users that wish a nearly stock system configuration, however either need root and busybox, or enjoy conducting more advanced tasks at the command line and wish a smooth root experience.
In addition some other small mini-fixes have been applied to the image in hope of a smooth experience.
Here is a list of the features and changes in the rom
Modified ADB to allow adb root to operate without changing the production build properties
Kernel patched to allow system remount
Busybox built from CM9 source tree and integrated into the rom
runparts (ie /system/etc/init.d functionality)
GPS lto fix thanks to waydownsouth
FDUpdater (ie system update) removed to not be prompt for an update you can't install.. if you want it the original app is in the system folder of the update.zip, (FDUpdater.apk) its not odexed so install normally)
Kernel modules md4.ko sha512_generic.ko and cifs.ko added to the rom (md4/sha512 is loaded on boot via an init.d script, users of cifs need to check the "Load cifs module" option in CifsManager.
Added Superuser
DHCP Infinite Lease bugfix (why has google not fixed this) applied as a patch to the framework.odex
Rom is still odexed (and I re-odexed the one changed odex for the DHCP patch)
Developers wanting more details or the source to anything I changed can see this detailed modification guide: http://pastebin.com/ApUjMDJ7
Note to anyone wishing to make a modification to the rom they are flashing, everything in the system folder of the update.zip is unchanged from the original rom. (when flashed the system is patched and augmented via various files and tools in the custom directory, also the boot image is pre-patched)
==~== Extras and Addons ==~==
** Overclocked test kernel: See my ezT20 kernel here (previously OCTestV3 here
(kernel last updated June 18th 2012)
** Disk IO enhancement: significantly increase diskio scores, and make the table slightly more responsive when reading/writing to flash: On this post
(diskIO last updated June 5th 2012)
==~== Tips and Tricks ==~==
This section is where I try to explain how to get the most of your tablet, and solutions to common complaints due to changes between versions.
-----) Rom "Bloat" (------
First half of what people call rom bloat is not quite true, (there is such a thing, and problems related to it)
Our tablets have 590MB system partition, a 97MB vendor partition, a 1GB cache partition, and the rest of your tablets space in a data partition (mine is 27GB, but if you have a smaller tablet model it will be less) All roms will have currently the same split between the partitions.
Its only that last partition that contains your data, the system/vendor partitions are by default read only, and the cache partition is temporary data.
System apps are on the two read only partitions, thus removing them for the most part will not cause more data to be available to your apps. Also this is storage space so having more "free" will not speed up your device (well as long as we are not too close to full.. and this rom is not)
Most of these apps play nice, they don't run unless you select them thus you can ignore they are on your tablet and all will be just as fast as if they were never installed
There is however one *Problem* Applications pre-installed that run constantly in the background that you the user are not interested in.
Solution: Freezing apps
* Goto Settings-> Apps-> All
* For any of the following that you do not use:
> Photo Browser 3D
> SocialJogger
> Acer Media
Select the app,
Choose Disable
Clear Data
If you use the app, obviously keep it enabled, also you can return to this screen and re-enable the app.
-----) Screen flickering/brightness oddities (------
I have had some brightness issues initially, simple fix was to go into settings->display->brightness uncheck auto bightness, lower the meter, and re-check auto brightness
-----) Sluggish system (------
Make sure on first boot you give the system some time (2h/3h after upgrading or re-installing where there is a large collection of media on the tablet) before measuring speed, as the system may be still sorting/indexing tablet data and will speed up when done.
Also while apps are installing the system may behave slower (if you have many market updates happening in the background)
Otherwise check running processes in settings to see if anything may be slowing down your tablet in the background (Settings -> Apps -> Running)
==~== Credits ==~==
civato - for his guide to installing the new bootloader and some testing of some of the tools I use to patch the rom up
waydownsouth - for the GPS patches (and work on CM9 for our tablets as it helped create some of the utilities in use here)
CyanogenMod and Team - For the idea of the root change, modifications to the bustybox build, and Koush's ClockworkMod recovery
vache - various insight all over XDA on how our device works (and leaks but this build is from the official OTA I recived)
Skrilax_CZ - for the unlocked bootlaoder, without which we couldn't run these roms
And the many others that provide development insight, source code, and examples here on XDA

2nd Post
reserved for future

Nice and congratulations with your release.
I will ad a link to this rom in the unlocked bootloader guide.

Overclocked kernel [May 23rd 2012]
(wow I think we can hear crickets in here..)
Anyway using the now released source code from acer, and richardtrip's OC patches from HC I now have an overclocked kernel.
As of V3 I also have the voltage controls patched up from richardtrip's kernel.
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Instructions are simple: flash from recovery
Links to the github source and other information on the AcerOCTest kernels is in this related notecard
While I've only tested it on this rom, the installer is using koush's anykernel logic (or one of my own flavors of that logic anyway) and thus this ought to cleanly install on any rom based on the stock ICS kernel regardless of the tweaks the rom creator may have added.)
Also I've not had much time to test so let me know if there are issues
----
List of all versions:
V3 - AcerOCTestV3_S.zip (md5: 6907e7585fedf534261cc8ebe23d824a) May 23rd 2012
V2 - AcerOCTestV2_S.zip (md5: da01a90dda3916ec55ebb62bbb1164f1) May 22rd 2012
V1 - no public binary (caused reboots on tablet sleep)

Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.

Jigga0o7 said:
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Click to expand...
Click to collapse
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
edit: although I'll look into it some may be a new verification in the updated kernel. the tegra2 OC logic is much more complicated than the msm logic I'm used to on the HTC dream.. I'm more worried about reboot-on-wake bugs I had in earlier revisions

ezterry said:
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
Click to expand...
Click to collapse
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.

Jigga0o7 said:
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Click to expand...
Click to collapse
looking closer its a but..
So now I have two OC tests I've made.. the first one I didn't publish because while it could go > 1.2 it crashed when you put the tab to sleep. (at least when USB wasn't connected)
This one crashes when you go over 1.2.
maybe if a combine them I can get something that works...

Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.

Jigga0o7 said:
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Click to expand...
Click to collapse
No.. well maybe but you not getting that far.. its a kernel BUG condition, meaning some code found some invalid input and refused to process it, instead triggered a reboot.. looking at the diff of mycode and the code in the CM thread.. no logic is different so i'll need to poke min/max rail voltages. (still sorting out all the voltages and CPU speeds.. the dream had it all in one large table .. here it seems spread out in various places between two files..)
(I'll also try to include the voltage manipulation patches just making sure things are stable first thus 1.2ghz is a better testing speed for me than trying to Max my device)
As for CM..it seems to have many interesting features.. but at some point I'm not sure its direction matches my interests.. (maybe its just become too much of a kitchen sink i don't know, that or too much now in aosp) I'm sure to look at it but probably start an aosp build with cherrypicked features I like.. until then this tweaked ics rom will need to do.

Fyi I haven't had a single issue on your kernel.

Been waiting on this! Thanks ezterry.

Jigga0o7 said:
Fyi I haven't had a single issue on your kernel.
Click to expand...
Click to collapse
Well next version will have voltage controls and working higher overclock speeds
(just ironing out some minor issues with the voltage control)

Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Just had a other pm today confirming it worked.
And I'm testing your modules and OC zImage with this modded in the boot.img-ramdisk (and my other tweaks) and I don't get any SoD , screen off , back on no problem.
Also confirming 1200 is max , over that it will reboot.

Ezterry,
Thanks!
very nice kernel, I flashed the 'civato' version to avoid SOD ...
Works nicely in 1.2 Ghz...
Btw, the old "No-Frills CPU control" apk doesn't apply the upper 1.2 Ghz frequency at Boot as asked.
Do you know another tool working to apply OC at boot?
(I'm using Civato's last version of flexreaper ROM)
=================================================================
>>>>> I have found a solution: I now use System Tuner PRO with its OC setting and it works <<<<<
=================================================================

civato said:
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Click to expand...
Click to collapse
.. I think this solution has nothing to do with the debug variable and everything to do with *forcing* the user to install a ICS kernel and stop messing around with the HC kernel they had earlier. (since you are installing a new boot.img)
So says the code anyway. If you want to prove it wrong after the crash + quick reboot get your users to dump the last_kmsg and output of dmesg so we can actually debug what is going on.. well unless its just the wrong kernel
But if the "obecalp" works to get some your users to install the right thing and so they fix there own problem.. so be it.
--
I have to inform users of my rom its no longer my rom if they install one of your (or anyone else's) full boot images and not to complain of any resulting bugs here.. If anyone with this rom has a SoD (none reported yet.. but I block installation on the old HC bootloader) let us know if you have such an issue. (just want to add if the full boot image was modified from the one in this rom, and intended for users of this rom that isn't an issue.. the issue is when its for another rom)
Its a bit different when you flash my update on another rom, since I only swap the kernel and leave the ramdisk as is, (by unpacking and repacking the boot.img) the rom designers changes stay intact.. well unless they had a kernel module that I've not included.. but even then we will need to re-build that module)
and you can test this after boot enter terminal and run echo '3> /sys/module/wakelock/parameters/debug_mask' that is the default.
(If it is disabled it just won't print the list of wakelocks to the kernel log on suspend..)

UPDATE @@
http://forum.xda-developers.com/showpost.php?p=26432810&postcount=4
ezterry said:
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Click to expand...
Click to collapse
Hopefully fixed the max speed bug, and added in the voltage controls.
Not much else yet has changed. but seems stable.
Its the same anykernel package as last time so it should cleanly swap the kernel (leaving the previous ram disk) for any ICS stock kernel based rom.
(Is there one app out there that actually knows how to successfully set *both* cores frequency and set voltage on boot, without giving the world access to the /sys files [so a malicious app cant overclock+fry the device or under clock it so it feels painfully slow]... soon I'll just write an init.d script for myself to echo the values directly into the kernel settings /rant)

I use setcpu.

civato said:
I use setcpu.
Click to expand...
Click to collapse
I don't like that he (and has always) granted global write permissions to the /sys/ files controlling the CPU/Voltage settings .. and it was acting flaky on voltage settings on boot.
Voltage Control looked good until a verification in /sys indicated if left the second CPU core at 1GHz
Now poking system tuner/system tuner pro.. many interesting features. Not sure they quite understand use root to write the value.. or set the file to your own ownership..
*ANYWAY*
you can check these yourself manually at the command line/adb shell:
CPU0: /sys/devices/system/cpu/cpu0/cpufreq
CPU1: /sys/devices/system/cpu/cpu1/cpufreq
current status of the voltages is in the readonly: frequency_voltage_table
list readonly of available frequencies is: scaling_available_frequencies
list readonly of available governors: scaling_available_governors
the current min frequency: scaling_min_freq
the current max frequenct: scaling_max_freq
the current cpu governor: scaling_governor
the current undervolt levels (negative values are over volting): UV_mV_table
UV_mV_table is in the same order as frequency_voltage_table, and if written to with the same number of values will update the voltage levels.

I got a question , why :
sha512_generic.ko = what does this do ?
modules.order = why does it need to know the order ?

[stop-dev][TWHK][cm7][flipout-mb511-ruth][testing] status: become stable

WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.

use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.

In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.

No phone to test
>.<
Sorry guy I can't help

May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.

Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.

sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards

phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)

I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^

everything is working except that when phone reboot version is still 2.1 and nothing changed :/

adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.

phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?

Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse

Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.

Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.

Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!

just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.

there are so many attachments here
please put them into #1
Great job, men!

netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:

finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other

[unofficial][linux3.4][native][tarchive][multirom]ArchLinuxARM release for N7 2013

This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483

looks interesting will give it a crack and see how it goes

thanks for the work. it boots impressingly fast.
castrwilliam said:
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Click to expand...
Click to collapse
if I activate the onboard keyboard ist shows at the bottom of the login screen. login works without password. when beeing logged in the keyboard is gone. I can see the keyboard symbol on the left besinde the speaker symbol but tapping on it doesn't trigger anything. also changing any options in the control center -> onboard settings have no effects. logging in without keyboard activated and then control center -> onboard settings has no effects either.
I cannot "adb shell" due to lack of permissions
Code:
# adb devices
List of devices attached
???????????? no permissions
and I'm not owning a bluetooth keyboard. so right now I can only play minesweeper - oh wait, it's not installed...

is there any way to rotate the screen as its really annoying having it in portrait all the time

Toby0897 said:
is there any way to rotate the screen as its really annoying having it in portrait all the time
Click to expand...
Click to collapse
Yeah it is in the monitor options but it's worthless since Xorg crashes when changing the rotation

Great stuff!
I would remove the KDE plasma etc packages as that desktop seemed to unusable. (Due to broken hw acceleration?).
what's next?

Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!

hugomc92 said:
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
Click to expand...
Click to collapse
You will need to install busybox for tar to work

daringblaze said:
You will need to install busybox for tar to work
Click to expand...
Click to collapse
Thank you very much!! That make tar to work!!
Gonna try archLinux ASAP!!
Thanks!

updates
Hi, great stuff!
After installing it, I tried to update arch (
Code:
sudo pacman -Syu
) but this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!

computer-whisperer said:
this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
Click to expand...
Click to collapse
Make sure you ignore xorg and mesa stuff. Add
Code:
IgnorePkg = glu mesa mesa-dri mesa-libgl xorg-server-common xorg-server-devel xorg-fonts-misc xproto libdrm
IgnoreGroup = xorg
to /etc/pacman.conf.
The list probably contains some extra entries, but works for me

It took xda 2 years, but they finally did it.
In all seriousness, props to you. I've been waiting for this for along time.

castrwilliam said:
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/......
Click to expand...
Click to collapse
Hi castrwilliam, would you mind sharing what step you went through to create arch_flo_20141210_multirom.tar.gz ?

Great work guys! I was looking for this for a really long time and i am writing this on my n7 with linux but i have a few questions:
1. is it possible to overclock(and how) because my n7 runs on 1.89ghz and 477mhz gpu in android with elementalx kernel and it would be nice to have some more power
2. can the screen be rotated so the hardware buttons are on top (i saw a post saying it chrashes but i cant even find the setting xD) because it would be alot easier to use the OTG cable
And thank you guys for making this happen, i love linux on the note 10.1 and im so glad to have this run it too(would be maaad if it can be overclocked )

Thank you for this wonderful package!
I recently updated all packages ) and iam trying to fix the issue without reinstall (challenge accepted)
It seems that the xorg-server 1.17 is the problem. I compiled. Freedreno and the freedreno mesa 10.3 and libdrn packages without success. The xserver is segfaulting when it loads libexa.so.
Now i try to downgrade to 1.16 . ive read that the xf86-video-freedreno-git package is not working with flo. Is that correct? Did youbuild this packages with modificationa?
I believe this is why i love arch. Its like lego for nerds or something

castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
What's NOT working

Hello, is there some instruction howto run (native) arch on nexus 4? I see only for n7, n10...

Hello, I have some trouble when I boot.
config: rastapop 5.1.1 (AOSP based) + last multirom v32A + Kernel w/ kexec-hardboot patch (Stock 5.1.1)
Installing archlinux correctly from the terminal emulator. Load it --> black screen (about 6seconds) --> Google Logo forever
Someone know what I can do for make it work ?

Cool I will give it a try.

How do I set selinux to permissive ?

Current status of my Note 3
Root,Unlocked bootloader,twrp recovery and the firmware is OF1.
The reason I think I need permissive mode is because I am having problems with trying to get linux deploy to work.
From reading some posts I have gathered that selinux might be the problem.
To get into permissive mode I need to replace the kernel I think, how is permissive mode done ?
thank you.

The phantomOne kernel ("hlte-vzw" version) seems to be permissive. You can use it with the AryaMod ROM if you like.*
There are kernel build-time configuration option(s) determining whether SELinux is (a) disabled, (b) alterable by kernel boot arguments (or post-boot changes), or (c) permanently enabled and immutable, and finally (d) either permissive or enforcing. In the case of (b) the default (absent a kernel boot command line argument) could be either permissive or enforcing.
Some of the above combinations are not used in practice - e.g. it makes little sense to be immutable and permissive.
In any event, you would have to see the kernel build configuration files to know what the exact setup was (or the kernel has /proc/config.gz enabled).
Typically a vendor will use "permissive" as a stepping stone towards getting full-up immutable, enforcing SElinux running without problems: the kernel will issue violation warnings without enforcing the SElinux constraints, so that kernel logs can be used to diagnose improper setups of SElinux execution contexts (domains) and filesystem extended attributes on a live testing system.
* I'm on NC4 bootloader; ymmv.

W T F no write access to ext sd card as default ?
still poking about trying to figure out why the linux install script's dont work.
I have discovered that as a default programs or apps dont have the permissions to write to the extsdcard . The extsdcard is read only. I think that actually is my problem.
where do I look to perminatly change my permissions on my extsdcard to 777 for all users and groups.
does android have somthing like an fstab file or mounting options ??

If it's any encouragement to you, I got the "Linux deploy" app to work on
AryaMod6.6 + phantomOne kernel (permissive SELinux).
I had similar troubles creating the initial container on the /sdcard, and I'm pretty sure that was just operator error because the interface is not intuitive and of course I completely failed to RTFM. So, maybe the container creation issue has nothing to do with SELinux at all.
Useful hint: with a default "linux" (==debian jessie ARM) profile container, the default username for all the services (httpd, sshd, vnc) is "android", and the initial passwords are found in two different places: under the "Settings" menu pick for httpd and telnetd, and under the little "inbox" icon menu for the profile for sshd and vnc. I had to use "apt-get install tightvncserver" to get vncserver up and running from the ssh command line. ("sudo /bin/bash" first).
I had to log in to the phone via adb and do a " netstat -n -a | grep 'tcp.*LISTEN' " to convince myself the various servers were up. That helped a bunch. httpd on :5080, telnetd on :5023, vncserver on :5901.
good luck, I struggled with it.
What are you going to use this for? I suppose if you have access to a full native-ARM Linux environment, perhaps it is easier to build native tools against libc without the constraints of bionic and the NDK?

bftb0 said:
If it's any encouragement to you, I got the "Linux deploy" app to work on
AryaMod6.6 + phantomOne kernel (permissive SELinux).
I had similar troubles creating the initial container on the /sdcard, and I'm pretty sure that was just operator error because the interface is not intuitive and of course I completely failed to RTFM. So, maybe the container creation issue has nothing to do with SELinux at all.
<SNIP>
What are you going to use this for? I suppose if you have access to a full native-ARM Linux environment, perhaps it is easier to build native tools against libc without the constraints of bionic and the NDK?
Click to expand...
Click to collapse
What I am trying to do is explore just how well I can really use this brilliantly wonderful device as my main computer. I have good reasons for this but there all related to my personal circumstances and I won't bore you with the details, sufice it to say that I am now living in a electricity/power scarce inviroment and a cell phone is about as power efficient as I can get and have reasonably powerfull hardware.
I had considered sbc's like the Rasb. pi but there are none that even come close to the capabilities of this phone.
GPS,wifi,cellular,acceleromiter etc.
In an Ideal world I could wipe android fully from the phone and load a distro of linux that fully supported all the hard ware of the note 3 giving me as fast and lean a computing enviroment to work with Or perhaps a duel boot configuration like grub boot either android or linux.

Phantom kernel and lss works great ..been going back and forth with the latest international roms since there's not too much happening on our Verizon forum.
Sent from my SM-N930F using Tapatalk

OPEN BETA for 17.1 UNOFFICIAL LineageOS T550 rom

BEFORE YOU decide to try this rom, please read all of post 1 and 2.
The UNOFFICIAL LineageOS 17.1 T550 ROM
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
Let me be clear, I have the SM-P550, NOT the SM-T550.
So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.
I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.
So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
The rom has the latest monthly 2021 security patches.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover
11. audio over bluetooth
What doesn't work
1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Why are you releasing a ROM for a tablet that you do not own?
A1) I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.
Q2) What if my app, xyz, doesn't work?
A2) I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit, not mine as I don't even have the T550.
Q3) Your rom is laggy and buggy.
A3) If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research newpipe, microg, youtube vanced, aurora store etc.
Q4) What TWRP should I use?
A4) Use 3.4.0.0. Get it at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
dl.twrp.me
Q5) Why should I use this rom?
A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.
Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.
Q7) Will you offer monthly updates with security patches?
A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.
Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.
Q9) Can I report a bug with respect to the rom?
A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.
Q10) Can I build this rom? Where are the source and kernel source files?
A10) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
aala27 - Repositories
aala27 has 7 repositories available. Follow their code on GitHub.
github.com
Q11) Okay, I understand the consequences and that this is beta rom and willing to take the risks outlined, now where can I find the rom?
A11) Downloads are at
retiredtab - Browse /SM-T550/17.1 at SourceForge.net
sourceforge.net

Hi rretiredtab
I have a T550 with the latest virsys image 16.0 from March 2020.
It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
I'm ready for a new challenge. If I can help you, please let me know.
Best regards
Schaagi

Hi retiredtab,
I ready to try this rom

Schaagi said:
I have a T550 with the latest virsys image 16.0 from March 2020. It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
Click to expand...
Click to collapse
My 16.0 rom for the SM-P550 is based on virsys repos. However, I was only able to make 2 builds using his repos before a LineageOS update in Sept 2020 caused it to get stuck at the boot animation.
Then I tried virsys 17.1 repo and it too gets stuck at the boot animation. I know virsys built crDroid Android 10 rom and uploaded it sometime June 2020, but his Android 10 repos on github are dated March 2020 so whatever patches he did to get crDroid working isn't on github.
I don't know if 17.1 will be faster than 16.0. The 17.1 builds, by default, use an overclocked CPU and GPU in the kernel code. However, I don't know if you will see any real world differences in performance from the overclocking.
In addition, I don't know if virsys March 16.0 March 2020 is overclocked or not. You can always download an utility like CPUinfo at
CPU Info | F-Droid - Free and Open Source Android App Repository
Information about device hardware and software
f-droid.org
to see if the CPU is running at 1.2Ghz or 1.6Ghz (overclocked).

@Schaagi and @Simone101, please let me know if the T550 ROM boots or not after you have installed it. I'm pretty sure it will, but would like to know ASAP.
Then, afterwards, you can let me know how it works over a 24 to 48 hour period. I'm interested to see if it randomly reboots or crashes.
As for speed and performance, just remember it's a 5 year old entry level tablet and unless LineageOS is written in assembler language, it will never match a top of the line model tablet.
Thank you.

I've installed your image as clean-install. It boots !!!
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
First installation without opengapps -ok
Second one with opengapps - ok
Restore Data from previous image - ok
As next I will try to install magisk.
Wow, good job. I will check it for the next days and give feedback later.
Best regards
Schaagi

Schaagi said:
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
Click to expand...
Click to collapse
Can you provide a screenshot of the error please?
I haven't seen the bluetooth error before on my SM-P550 and I reboot my SM-P550 a lot because I'm always flashing new builds.
I don't use bluetooth at all, but when I turn it on, I can see my neighbor's 65 inch TV. Also, I can pair two tablets together using bluetooth.

Meanwhile I have installed Magisk 21.1 and it works too
I've attached 2 screenshots from Bluetooth error.

Schaagi said:
I've attached 2 screenshots from Bluetooth error.
Click to expand...
Click to collapse
The above is why we need BETA testers.
Okay, I ran into the bluetooth error problem on the SM-T350 and it was due to a missing bluetooth library.
In my SM-T350, I have
Code:
# RT 17.1 copy bluetooth file otherwise bluetooth keeps crashing
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/vendor/lib/libbtnv.so:$(TARGET_COPY_OUT_VENDOR)/lib/libbtnv.so
Those 3 lines of code are not in the T550 build. It's easy to add and I can create another BETA build. It's building right now and probably be done in the next 2 hours or so.
If you want to add the libbtnv.so file yourself, here are the instructions
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libbtnv.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Click download.
5) Goto the directory where the libbtnv.so is saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$ adb push libbtnv.so /system/vendor/lib/libbtnv.so
libbtnv.so: 1 file pushed, 0 skipped. 48.5 MB/s (16128 bytes in 0.000s)
8) Check to make sure file was pushed.
Code:
$ adb shell ls -al /system/vendor/lib/libbtnv.so
-rw-r--r-- 1 root root 16128 Dec 19 21:24 /system/vendor/lib/libbtnv.so
9) Reboot into system and bluetooth error should be gone.
OR
Just wait until my next build is done to get rid of the bluetooth errors. I'm confident the error is due to the missing bluetooth library file.
I will send you and Simone101 a PM when the new build is done.

The new BETA build is finished, but having problems uploading to host server right now. I will try again in a couple of hours to upload. I will PM when I get it uploaded.

I've installed the new image and bluetooth error has gone.But I'didn't test the functionality of bluetooth at the moment.
Will check more in detail and inform you about the results. Thank you.
Regards
Schaagi

@retiredtab
I want to test your ROM , where I can download it.
At the moment I use the cdroid 10 by virsys
My CPU runs at performance mode with 1600 MHz.

bierma32 said:
At the moment I use the cdroid 10 by virsys
Click to expand...
Click to collapse
Over at the T550 thread, it seems that some people who are using crDroid 10 are reporting
1) camera not working
2) brightness not working
3) browser crash (that's you)
#1 and #2 work on my build. As for #3, if you are using the built in Jelly browser, I have noticed that if you open more than 4 windows, it crashes sometimes.
While not perfect, I found that smartcookieweb app works better than Jelly.
Releases · CookieJarApps/SmartCookieWeb
A secure, open source web browser for Android. Contribute to CookieJarApps/SmartCookieWeb development by creating an account on GitHub.
github.com
The Brave browser seems to work the most reliable. You can use Aurora store to download it from play store or try downloading brave apk somewhere.
On a daily basis, I use smartcookieweb as it has built in adblocker and suits my daily browsing needs.

@retiredtab
Both cameras works on Cdroid for me.
Yes, browsers crashes after some times, I use opera mini.

Bluetooth works for, tested sending and recive images.
GPS is not working, will try it again next time.
Magisk 21 works.
WiFi works.

Hi retiredtab,
Nice to see that anybody has try to give us an update for this fossile
Please let me knoe where can I download and test your build.
regards,
L

bierma32 said:
GPS is not working
Click to expand...
Click to collapse
No need to retest GPS. I already know what's wrong. This is the same problem I had with the T350.
The T550 build is missing the commands
Code:
# GPS
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/lib/libloc_api_v02.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_api_v02.so \
vendor/samsung/msm8916-common/proprietary/lib/libloc_ds_api.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_ds_api.so
Now I did test the T550 build on my P550, but it looks like when I made the final image, some of my scripts or commits didn't get copied, like the above, over when I initially changed some P550 naming/parameters to T550.
Some background. I had only 1 hard drive for the P550 and T550 code. I did test bluetooth and gps on my P550 and both work.
After I tested everything, I then later split the P550 onto one hard drive and the T550 to another so I wouldn't get confused when compiling and making changes. I suspect now that I forgot to copy over my T350 script to fix gps and bluetooth onto the new T550 drive.
To fix gps without having to re-download another 440MB file,
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libloc_ds_api.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
and
proprietary_vendor_samsung/libloc_api_v02.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Download both files above (libloc_ds_api.so and libloc_api_v02.so).
5) Goto the directory where both are saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$adb push libloc_api_v02.so /system/vendor/lib/libloc_api_v02.so
libloc_api_v02.so: 1 file pushed, 0 skipped. 7.6 MB/s (116316 bytes in 0.015s)
$adb push libloc_ds_api.so /system/vendor/lib/libloc_ds_api.so
libloc_ds_api.so: 1 file pushed, 0 skipped. 29.5 MB/s (26132 bytes in 0.001s)
8) Check that both files exist.
$adb shell ls -al /system/vendor/lib/libloc_api_v02.so
-rw-r--r-- 1 root root 116316 Dec 7 2020 /system/vendor/lib/libloc_api_v02.so
$adb shell ls -al /system/vendor/lib/libloc_ds_api.so
-rw-r--r-- 1 root root 26132 Dec 7 2020 /system/vendor/lib/libloc_ds_api.so
9) Reboot into system and GPS should be work now.
I'm making a new BETA image again and before I upload it, I will retest everything again on my P550. It's a bit awkard as everything is mapped backwards on the X-axis.
I'll post here when it's up.

Well it was around 1AM in the morning when I saw the gps not working post and now it's 2:13AM. I'm just waiting for the last 5 minutes of my new build, but the host server is having major problems right now.
So I'm going to sleep and will try uploading the new image tomorrow after I retest everything with the P550 running the T550 image. Everything will be mapped backwards for me on the X-axis while testing.
Dec 21 BETA build up. Androidfilehost is having major problems so I put it up on sourceforge.net. No way I could go to sleep with this hanging over my head. It's 2:30AM. Now I'm going to sleep in tomorrow.
Dec 21 build has gps fix.

Ooh i want really like to test!

Database Users

welcome